edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] allocating <SCRIPT> to <HEAD> or <BODY>
Date: Wed, 1 Mar 2017 18:43:01 -0800 (PST)	[thread overview]
Message-ID: <alpine.LRH.2.03.1703011828460.25542@carhart.net> (raw)



One of the tests in acid3 that fails is test #0 out of 0-99.
There may be multiple causes but I think I found one.  I was looking at 
#0 because I wanted to take it from the top.

test #0 says this
var scripts = document.getElementsByTagName('script');
document.body.removeChild(scripts[scripts.length-1]);

The problem is that the script it is trying to find has parentNode head 
and not body according to how we currently allocate them.

The acid3 page has some scripts out in limbo that are not inside of either
<HEAD></HEAD> or <BODY></BODY>.  For instance, the page begins like this

<html>
  <title>The Acid3 Test</title>
  <script type="text/javascript">
   var startTime = new Date();
  </script>


This might be a tidy question.  What should be the tree presence for 
scripts that are found out in limbo?  In other words, if you had,

<HTML>1<HEAD>2</HEAD>3<BODY>4</BODY>5</HTML>

>From what branch should 1, 3 and 5 descend?


thanks
Kevin


             reply	other threads:[~2017-03-02  2:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  2:43 Kevin Carhart [this message]
2017-03-02 12:00 ` Karl Dahlke
2017-03-02 18:11   ` Kevin Carhart
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.1703011828460.25542@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).