From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] allocating <SCRIPT> to <HEAD> or <BODY>
Date: Thu, 2 Mar 2017 10:11:26 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1703020919420.5244@carhart.net> (raw)
In-Reply-To: <20170202070056.eklhad@comcast.net>
On Thu, 2 Mar 2017, Karl Dahlke wrote:
>> One of the tests in acid3 that fails is test #0 out of 0-99.
>
> Must they run in order?
No... no, I don't think they have to, I think they are autonomous or there
may be some grouping around topics, like maybe 70-80 is one theme and
80-90 is another theme, but I don't think 0 is a prerequisite of the rest.
I think we are passing about one quarter or 22/100 right now, but that
number may go up in a choppy way.
On thinking about it more and trying some sample html against one of the
old pre-tidy5, "validate my html and show me my errors" web pages, I think
tidy is correct. This is a settled, venerable task that it has done for
decades, so if you want to know the correct placement, work backwards and
whatever tidy is doing, that's where the scripts need to go. Thanks tidy
and tidy5 developers!
So I think I misdiagnosed this. The reason why the test
code can't find the script in body is, check out how ugly and baroque the
script code is..
<script type="text/javascript">document.write('<map name=""><area
href="" shape="rect" coords="2,2,4,4" alt="<\'>"><iframe
src="empty.png">FAIL<\/iframe><iframe
src="empty.txt">FAIL<\/iframe><iframe src="empty.html"
id="selectors"><\/iframe><form action="" name="form"><input
type=HIDDEN><\/form><table><tr><td><p><\/tbody>
<\/table><\/map>');</script>
It's clearly something to do with the interaction between a script,
document.write, iframes and embedded html with backslashes and quoting.
Still interesting for later, but I may have barked up the wrong tree.
thanks
Kevin
next prev parent reply other threads:[~2017-03-02 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 2:43 Kevin Carhart
2017-03-02 12:00 ` Karl Dahlke
2017-03-02 18:11 ` Kevin Carhart [this message]
2017-03-02 19:56 ` Chris Brannon
2017-03-03 3:24 ` Karl Dahlke
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.1703020919420.5244@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).