- From: inoas via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Oct 2017 12:51:28 +0000
- To: public-css-archive@w3.org
> From what I understand of the current state of css usage, with websites moving towards component-splitting of their files instead of type-splitting for their files, stylesheets files used in development have grown smaller and smaller, and targetted to specific portions of the application; using source order makes more sense than using the specificity cascade at that scale. You still want specificity rules for more generic theming purposes, and to allow the style of one component to override its sub component' styles if needed, but "local state" of a component is something people don't want to have an impact on specificity, hence this proposal generating zero specificity. ... and ... > While just thinking about how to manage the sublevels of specificity makes me a bit dizzy. Again: Would declarative-shadow DOMs help because they could reset styles and work around specificity issues on a component based level? -- GitHub Notification of comment by inoas Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1170#issuecomment-333831620 using your GitHub account
Received on Tuesday, 3 October 2017 12:51:17 UTC