Re: [csswg-drafts] [css-cascade] What are the proper "levels" for managing Cascade Layers? (#4969)

Our previous discussions on this suggested that we needed more than a single additional layer, but that we could generally solve each individual use-case with *three* built-in layers - "defaults", "normal", and "override" (along with their inverted !important versions). 

I think we also definitely still need to address the "scoping" of 3rd-party stuff, so they can use layers for their own purposes without necessarily having an effect on your layer usage. The important thing about providing predefined layers is that it allows us to reasonably do *non*-scoped stuff without complicated aliasing mechanisms (which custom names/ordering would require).

GitHub Notification of comment by tabatkins
Please view or discuss this issue at using your GitHub account

Received on Monday, 27 July 2020 23:32:08 UTC