- From: Philip Walton via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Sep 2017 19:30:45 +0000
- To: public-css-archive@w3.org
> Do we want to stick with this "something that makes its contents specificity-0", or try and generalize this to solve specificity hacks more generally? I'm in favor of a generalized approach. What about something that just turns off specificity at the stylesheet level, and for those stylesheets everything is order based? This would allow authors to easily control when they wanted specificity to work as an override and when they wanted to ignored it and treat it purely as a query. This would also help with resets and third-party stylesheets, and make it much easier for them to never clash with first-party styles. -- GitHub Notification of comment by philipwalton Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1170#issuecomment-329878248 using your GitHub account
Received on Friday, 15 September 2017 19:31:06 UTC