- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Sep 2017 04:07:29 +0000
- To: public-css-archive@w3.org
As @FremyCompany mentioned, I've toyed with a few ideas in this space - primarily enforcing a specificity score at the stylesheet level. That said, there is the potential for more author confusion in this space as you're essentially introducing another layer of specificity (eg: on or off) in addition to the other scores we provide to selectors. The only reason I had opted for stylesheet level (I initially wanted to just opt for off/on for an entire document) is because with components you won't have the same control over whether the components you may be utilizing want/need to cascade and depend on specificity. I would discourage this one selector being the only selector that nullifies the specificity because that is even more confusing to the additional layer IMO. I think if we do decide this is worth addressing then we should really consider all of the use cases and the way to make this as intuitive to authors as possible. -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1170#issuecomment-330423491 using your GitHub account
Received on Tuesday, 19 September 2017 04:07:21 UTC