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 10540 - Please say that 'list of scripts that will execute when the document has finished parsing' is coupled with the parser--not the document
Summary: Please say that 'list of scripts that will execute when the document has fini...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-03 06:48 UTC by Henri Sivonen
Modified: 2010-10-04 13:54 UTC (History)
4 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-09-03 06:48:45 UTC 
The spec doesn't make it clear which 'list of scripts that will execute when the document has finished parsing' defer scripts end up on when the parser inserts a defer script into a document that isn't the document whose active parser the parser is.

Please make it clear that the defer script ends up on a 'list of scripts that will execute when the document has finished parsing' associated with the parser and blocks the load event on the document whose active parser the parser is--not the load event of the owner doc of the script node (which might not be the same document).

Rationale: The processing of the 'list of scripts that will execute when the document has finished parsing' happens relative to the progress of the parse.
Comment 1 Ian 'Hixie' Hickson 2010-09-25 21:34:35 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: Partially Accepted
Change Description: see diff given below
Rationale: I agree with you as far as the  'list of scripts that will execute when the document has finished parsing' stuff goes (I've even gone further and defined other things that were similarly vague — see diff) but why change the load event delaying? Does anything else delay the load event of another document than its owner document?
Comment 2 Henri Sivonen 2010-09-28 11:48:46 UTC 
(In reply to comment #1)
> Rationale: I agree with you as far as the  'list of scripts that will execute
> when the document has finished parsing' stuff goes (I've even gone further and
> defined other things that were similarly vague — see diff) but why change the
> load event delaying?

At least Gecko implements load delaying by grouping pending network requests into "load groups". Regrouping the requests when a node is moved between documents would be added complexity to address an edge case.

> Does anything else delay the load event of another
> document than its owner document?

I don't know. I haven't tested what happens if an <img> is moved between documents between the start and end of the image load. My expectation is that the image load would keep delaying the load event of the document that the image was in when the load started.