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

> 1. Entire files, via html (e.g. <link> & <style>)
> 2. Entire files, via css rules (e.g. CSS @import)
> 3. One or more selector blocks, via css conditionals (e.g. @origin)
> 4. Individual declarations, via flags (e.g. !<origin>)

The current [Cascade 5 draft](https://drafts.csswg.org/css-cascade-5/) allows nesting layers, using an `@layer` rule for conditional code-blocks and stylesheet imports. My current thinking:

1. (link/style attribute) **TBD/yes**: I think a layer attribute would be useful to avoid chaining imports
2. (import) **yes**: `@layer url();` (syntax marked for discussion)
3. (at-rule) **yes**: `@layer {}` 
4. (!flag) **TBD/no**: I don't think it makes sense at this point to attempt any sort of arbitrary `!layer` flag on individual properties, but a simpler binary `!default` has been proposed elsewhere, and might be interesting

-- 
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4969#issuecomment-754901234 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 5 January 2021 21:10:38 UTC