- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Apr 2020 16:53:48 +0000
- To: public-css-archive@w3.org
> This is really a layer of cascade between origins and specificity. Is it? I mean, we could invent another category to slot in there, but what benefit do we gain from that? I think we'd actually lose some functionality by doing so. Considering it as a separate layer means that normal vs !important still works per the normal origin rules, meaning that an !important rule *definitely* wins over an normal rule, regardless of the relative orders of the custom "layers". I think at least some of the use-cases for custom origins want this to *not* be the case, and instead for a set of rules to have both its normal and !important rules scoped together and "weaker" than another set of rules - in particular, the "upgrading CSS, so we put the legacy CSS into a weaker origin and let the new CSS live in a stronger origin" seems to want that. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4981#issuecomment-621975440 using your GitHub account
Received on Thursday, 30 April 2020 16:53:49 UTC