W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

[Bug 7926] New: Undefine insertion point if parser on call stack doing anything other than running script element

From: <bugzilla@wiggum.w3.org>
Date: Thu, 15 Oct 2009 09:01:35 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-7926-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7926

           Summary: Undefine insertion point if parser on call stack doing
                    anything other than running script element
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Please make the insertion point undefined where the current spec would
otherwise make it defined if the HTML parser whose insertion point is in
question is on the call stack performing a DOM operation other than running a
script element upon </script>.

Rationale:
If document.write() can call into the parser in response to more or less any
parser-performed DOM operation (due to XBL bindings attaching to
parser-inserted nodes, due to legacy synchronous events firing when stuff is
inserted into the DOM), speculative parsing (in the network case) and
notification batching (to avoid running the CSS parts of the layout engine on a
per-DOM operation basis) become pointlessly hard.


-- 
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 Thursday, 15 October 2009 09:01:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 October 2009 09:01:39 GMT