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 20958 - [Shadow]: Consider dropping resetStyleInheritance in favor of a CSS property
Summary: [Shadow]: Consider dropping resetStyleInheritance in favor of a CSS property
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Hayato Ito
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 22715
  Show dependency tree / graph
 
Reported: 2013-02-12 00:02 UTC by Dimitri Glazkov
Modified: 2014-02-12 05:28 UTC (History)
2 users (show)

See Also:

Attachments

Description Dimitri Glazkov 2013-02-12 00:02:04 UTC 
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.
Comment 1 Dimitri Glazkov 2013-07-17 21:55:41 UTC 
This is doable now.