From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] script in tree of document.written elements?
Date: Tue, 15 Aug 2017 20:29:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1708152006320.7802@carhart.net> (raw)
In-Reply-To: <20170715225338.eklhad@comcast.net>
On Tue, 15 Aug 2017, Karl Dahlke wrote:
> 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.
Thank you for wrangling it in the first place. I think it's
semi-deprecated or Considered Harmful. There are various articles
frowning on it. So it's one of those annoying constructs that shouldn't
be used, but here it is in the tests itself.
Okay. I just opened hello.html in firefox and firebug. It puts the P
immediately after the script. The P has parentNode body. <Script> is
not part of its tree branch.
I'm also in acid3.acidtests.org in firebug right now to verify with this.
I'm opening up the document.forms. There is only one and it is one of
those tags that is part of the document.write inside of the last script,
so I think it's an illustrative piece of evidence and it's easy to make
sure you're on the element you want to be on.
document.form[0].parentNode is map, and
document.form[0].parentNode.parentNode is body
> 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.
I think that's right. And with script omitted from their descendancy
trail/tree branch. Could this actually be tidy-related?
This is going to be good.
next prev parent reply other threads:[~2017-08-16 3:29 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
2017-08-16 3:29 ` Kevin Carhart [this message]
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=alpine.LRH.2.03.1708152006320.7802@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).