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 10542 - Please associate a "style sheet blocking scripts" with its inserter-parser--not with it's Document
Summary: Please associate a "style sheet blocking scripts" with its inserter-parser--n...
Status: RESOLVED NEEDSINFO
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 08:00 UTC by Henri Sivonen
Modified: 2010-11-11 22:41 UTC (History)
4 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-09-03 08:00:55 UTC 
Please make a style sheet blocking scripts block parser-inserted scripts inserted by the same parser that inserted the sheet regardless of the owner doc of either the sheet or the scripts.

Scripts getting blocked is something that affects the inserter parser and it doesn't make sense to fragment aspects of the blocking across potentially multiple parsers if stuff moves during the parse.
Comment 1 Ian 'Hixie' Hickson 2010-09-25 21:58:46 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: Did Not Understand Request
Change Description: no spec change
Rationale: As currently defined, the style sheet blocking stuff doesn't get invoked cross-document at all. Doesn't that make this moot? (If it does get invoked in a case I didn't consider, let's just make it not get invoked, that would be a better solution than making things "work" cross-document, IMHO.)
Comment 2 Ian 'Hixie' Hickson 2010-11-11 22:41:42 UTC 
This ended up getting defined as you requested, right?