- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Feb 2013 00:02:04 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20958 Bug ID: 20958 Summary: [Shadow]: Consider dropping resetStyleInheritance in favor of a CSS property Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: dglazkov@chromium.org QA Contact: public-webapps-bugzilla@w3.org Blocks: 14978 >From Tab: http://lists.w3.org/Archives/Public/public-webapps/2013JanMar/0353.html --- ... dropping resetStyleInheritance in favor of CSS's new 'all' property <http://dev.w3.org/csswg/css3-cascade/#all-shorthand>. Doing so would be fine, technically - the property accomplishes the same thing as the attribute - but it falls down on usability. We want to *default* to having an inheritance shield, and let the author lower it if they choose, but you can't "unset" a property; if we start with "all: default" set, the author can't remove the declaration and lower the shield. If we kept the attribute and simply implemented it as the 'all' property using an attribute selector, though, it all works out. Also see bug 20957 for more context. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 12 February 2013 00:02:06 UTC