W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > June 2010

[Bug 9983] New: [parser] Insertion point not saved for external scripts

From: <bugzilla@jessica.w3.org>
Date: Tue, 22 Jun 2010 21:32:51 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9983-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9983

           Summary: [parser] Insertion point not saved for external
                    scripts
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P1
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: w3c@adambarth.com
         QAContact: public-html-bugzilla@w3.org
                CC: hsivonen@iki.fi, mike@w3.org, public-html@w3.org


In step 8 of
<http://www.whatwg.org/specs/web-apps/current-work/#running-a-script>, the spec
adds external scripts to the
<http://www.whatwg.org/specs/web-apps/current-work/#set-of-scripts-that-will-execute-as-soon-as-possible>.
 When the fetching algorithm is complete, the spec invokes
<http://www.whatwg.org/specs/web-apps/current-work/#executing-a-script-block>. 
However, that sequence of steps does not save the current insertion point
(among other things), which seems very unlikely to be compatible with the web.

In implementing the above requirement in WebKit, we assumed the spec meant to
invoke
<http://www.whatwg.org/specs/web-apps/current-work/#scriptTagParserResumes>,
which saves the current insertion point (and does other things that would make
sense at that point).  Should we change the spec to say this explicitly?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 22 June 2010 21:32:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 June 2010 21:32:57 GMT