13059 2011-06-25 12:47:35 +0000 add a disabled attribute to link and style elements 2011-08-14 06:21:48 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX P5 enhancement --- 1 daniel.glazman contributor ayg ian mike mounir public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 50313 0 daniel.glazman 2011-06-25 12:47:35 +0000 (note: this was submitted as an HTML4 erratum looooong ago to the XHTML2 WG ; I am surprised the current HTML WG did not get it in the list of HTML4 errata) The DOM Level 2 offers a boolean 'disabled' attribute on the StyleSheet interface. This boolean attribute is _extremely_ important to content editors because it allows to see how a given stylesheet affects the rendering of a document. But this boolean DOM attribute has _always_ raised an issue: it's impossible to save the enabled/disabled status of a stylesheet and that is a serious problem for content editors. I then recommend the addition of a companion html 'disabled' attribute on <link> and <style> elements matching exactly the DOM one. 50333 1 ayg 2011-06-26 22:38:22 +0000 What are specific use-cases where this is a serious problem for content editors? 50353 2 daniel.glazman 2011-06-27 05:36:54 +0000 (In reply to comment #1) > What are specific use-cases where this is a serious problem for content > editors? Ability to save the current status of the document in the editor ???? 53458 3 mike 2011-08-04 05:14:03 +0000 mass-move component to LC1 54920 4 ian 2011-08-14 06:21:48 +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: Why would you want to publish a file with a disabled style sheet? If the need is just for round-tripping during editing, then there's no need for the editor to limit itself to the HTML standard. Just use a custom attribute documented in a spec that applies to the documents used during editing. You'll need something similar to handle all manner of other round-tripping complications, like whitespace around the DOCTYPE or between attributes, the order of attributes, values in input controls when those aren't the default values, the current alternative style sheet set selection, the current scroll position if it doesn't match an ID, etc etc etc. If you actually want to publish a disabled style sheet, just comment it out.