W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11191] Run scripts based on a parser flag rather than on being a fragment parser

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Jan 2011 12:15:28 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PgFto-0004rW-K0@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11191

--- Comment #4 from Henri Sivonen <hsivonen@iki.fi> 2011-01-21 12:15:28 UTC ---
(In reply to comment #3)
> Running the fragment parser with scripts enabled is likely to have very
> different results than what one might expect,

Indeed.

> since the fragment parser is
> defined as parsing into a new document and then regrafting the nodes. Could you
> elaborate further on what exactly you need?

That when scripts are enabled, the result of the fragment parsing algorithm is
a document fragment that contain script element nodes whose 'already started'
and 'parser-inserted' flags haven't been set.

> What are the semantics you want for
> running scripts?

The same as when inserting a manually-constructed DOM fragment into a document.

> What scripts should run? 

All scripts whose type is a supported language.

> How should they interact with
> document.write(), async scripts, the event loop, etc? What if there are
> re-entrant invokations of this algorithm? etc

Exactly as if the fragment had been constructed with document.createElement and
appendChild.

-- 
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 Friday, 21 January 2011 12:15:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 January 2011 12:15:31 GMT