This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10541 - Make parser-inserted scripts delay the load event of the document whose active parser the inserter parser is
Summary: Make parser-inserted scripts delay the load event of the document whose activ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P1 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 06:54 UTC by Henri Sivonen
Modified: 2010-10-04 14:48 UTC (History)
4 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-09-03 06:54:12 UTC 
The spec says "Fetching an external script must delay the load event of the element's document until the task that is queued by the networking task source once the resource has been fetched (defined above) has been run."

When the parser ends up inserting a script into a document that isn't the document whose active parser the parser is, it is inconvenient to have the parser blocking, unblocking and insertion point management stay with the parser while making the load event delaying happen with a document that isn't the document being parsed.

Please make parser-inserted scripts delay the load event of the document whose active parser the inserter parser is.
Comment 1 Ian 'Hixie' Hickson 2010-09-25 21:56:17 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: I agree that it may be inconvenient to implement, and I will grant that authors doing this are hardly people we should be optimising for, but wouldn't this mark the first time something could delay the load event of a document that wasn't its owner document? That seems like an invariant we should be very wary about breaking.
Comment 2 Henri Sivonen 2010-09-28 11:50:20 UTC 
Did you happen to test what different browsers do?