From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Churning timers / I'd like to submit 3 things today
Date: Mon, 30 Jan 2017 15:33:45 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1701301455570.7206@carhart.net> (raw)
In-Reply-To: <20170030060040.eklhad@comcast.net>
Wooo, this is great lately!
> Ok I think I fixed the node tree problem. It was a silly silly silly
> mistake.
So the thing with "can't create tag blah" is done with? That's awesome.
I suspected it wasn't ideal to add things to tagInfo one by one.
Something seemed awry about adding canvas, video, bootstrap and on and on.
> You can type and type and nothing happens.
> Hit control c and get the usual "type qt to quit" message, but still you have no access.
> You have to kill the process. At least that's what happens over here.
I have definitely hit these before.
Other things bubbling up that I need to submit and haven't yet. These
four are four reasons why nasa.gov isn't working, maybe among other
problems too.
- document.querySelectorAll is going to come up. It's like the selections
made by getElementsByTagName, etc, except that it uses a language within
a language, for selection by CSS. I suggest maybe plugging in outside code
to take care of it. I predict we are going to want to have a discussion
about what to do about this thing.
- domLink TAGACT_META so that metas are part of document.head.childNodes
and JS can use their contents
- TidyDropEmptyElems no and TidyDropEmptyParas no in html-tidy.c
- I think there needs to be an Option.prototype block along with our
sets of element types in startwindow. It's asking for the
attribute-related methods, like Option.get
Could I do 2,3 and 4 today to get them out of our hair, and do they sound
acceptable? querySelectorAll is going to be more of a pain in the butt.
thanks
Kevin
next prev parent reply other threads:[~2017-01-30 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 11:00 [Edbrowse-dev] Churning Timers Karl Dahlke
2017-01-30 23:33 ` Kevin Carhart [this message]
2017-01-30 23:37 ` [Edbrowse-dev] Churning timers / I'd like to submit 3 things today Kevin Carhart
2017-01-31 2:31 ` [Edbrowse-dev] Churning timers / I'd like to submit 3 things Karl Dahlke
2017-01-31 18:47 ` Adam Thompson
2017-01-31 19:27 ` [Edbrowse-dev] Churning Timers Adam Thompson
2017-02-01 0:38 ` Kevin Carhart
2017-02-01 0:52 ` [Edbrowse-dev] acidtests script 8 Kevin Carhart
2017-02-02 1:16 ` [Edbrowse-dev] acidtests.org Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.03.1701301455570.7206@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).