12251 2011-03-05 20:51:54 +0000 The idea of limited-scope style elements is useful, but it causes compability issues. Current browsers ignore the scope attribute and apply the style to the entire document. It is probably better (safe) to ignore a style sheet that is meant to be scoped t 2011-08-04 05:05:01 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#the-style-element P3 normal --- 1 contributor ian ayg ian jackalmage jonas julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 46418 0 contributor 2011-03-05 20:51:54 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html Section: http://www.whatwg.org/specs/web-apps/current-work/#the-style-element Comment: The idea of limited-scope style elements is useful, but it causes compability issues. Current browsers ignore the scope attribute and apply the style to the entire document. It is probably better (safe) to ignore a style sheet that is meant to be scoped than to apply it globally. I propose that the scoped attribute be removed and a new MIME type, say text/css-scoped, be defined. A scoped style element would then be written as a normal style element, just with a type attribute mentioning the new MIME type. Posted from: 88.114.29.18 User agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fi; rv:1.9.2.14) Gecko/20110218 Firefox/3.6.14 ( .NET CLR 3.5.30729) 46419 1 julian.reschke 2011-03-05 21:09:32 +0000 Alternatively, maybe the current browser behavior should be fixed instead? 46420 2 jackalmage 2011-03-05 22:59:41 +0000 Agreed with Julian. Browsers should support @scoped, and in the meantime people shouldn't be using @scoped. 48288 3 ian 2011-05-07 18:49:20 +0000 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: Until browsers support scoped="", there's a simple workaround to fix this: put an id="" on the <style> element's parent, and put #id in the front of every selector. 52876 4 mike 2011-08-04 05:05:01 +0000 mass-moved component to LC1