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

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

From: <bugzilla@wiggum.w3.org>
Date: Wed, 21 Oct 2009 09:42:18 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1N0Xhy-0007Wt-3z@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7926


Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |




--- Comment #2 from Henri Sivonen <hsivonen@iki.fi>  2009-10-21 09:42:17 ---
(In reply to comment #1)
> How would you have me handle document.open()ed pages, which always have the
> insertion point set?

I suggest making the undefinition rule in this bug report override the
definition rule from the current spec: That is, I propose undefining the
insertion point in the document.open() case when the script-created parser
itself is on the call stack performing a DOM operation (other than running
script upon </script>). The purpose is to keep the implementation sane in the
case of XBL constructors, legacy link element insertion events or the SVG load
event firing from a script-created parser.

Concretely, I'm asking you to legitimize the !mExecutor->IsFlushing() check in
IsInsertionPointDefined() in the patch on
https://bugzilla.mozilla.org/show_bug.cgi?id=503473


-- 
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 Wednesday, 21 October 2009 09:42:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 October 2009 09:42:20 GMT