From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] script in tree of document.written elements?
Date: Tue, 15 Aug 2017 22:53:38 -0400 [thread overview]
Message-ID: <20170715225338.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1708151706370.12666@carhart.net>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
It was not at all clear to me, is not at all clear to me, where to put the objects that result from document.write.
innerHTML is obvious, document.write isnot.
I thought they should parse under the script that does the document.write, that is reasonable, rational, but not based on any spec or anything.
If the document.write is from an onload or onclick function, not an obvious script,
then I put the objects in a nowhere place wherein they still get rendered so you see them in the buffer but aren't part of the js tree at all.
That can't be right.
See html.c line 559.
The short answer is, I could probably put them just about anywhere.
They could all go under document.body if that is where they're suppose to go.
Or document. You'll have to review the test and infer where they belong.
Karl Dahlke
next prev parent reply other threads:[~2017-08-16 2:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 19:46 [Edbrowse-dev] acid3 log! Kevin Carhart
2017-08-15 22:44 ` Karl Dahlke
2017-08-15 23:04 ` Kevin Carhart
2017-08-15 23:38 ` Karl Dahlke
2017-08-16 0:18 ` [Edbrowse-dev] script in tree of document.written elements? Kevin Carhart
2017-08-16 2:53 ` Karl Dahlke [this message]
2017-08-16 3:29 ` Kevin Carhart
2017-08-16 3:32 ` Kevin Carhart
[not found] <20170716000647.eklhad@comcast.net>
2017-08-16 4:54 ` 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=20170715225338.eklhad@comcast.net \
--to=eklhad@comcast.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).