From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] allocating <SCRIPT> to <HEAD> or <BODY>
Date: Thu, 02 Mar 2017 11:56:27 -0800 [thread overview]
Message-ID: <87mvd3mp04.fsf@the-brannons.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1703020919420.5244@carhart.net> (Kevin Carhart's message of "Thu, 2 Mar 2017 10:11:26 -0800 (PST)")
Kevin Carhart <kevin@carhart.net> writes:
> 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..
Not necessarily. In the case where script comes between head and body,
tidy5 adds it to head. So I wonder, in our DOM, is the missing script
there, rather than in body? If so, we've got another parsing problem.
-- Chris
next prev parent reply other threads:[~2017-03-02 19:56 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
2017-03-02 19:56 ` Chris Brannon [this message]
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=87mvd3mp04.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--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).