Re: [csswg-drafts] [css-cascade-5] Allow authors to explicitly place unlayered styles in the cascade layer order (#6323)

Is there a reason why "unlayered" should not be a keyword to represent the placement of the unlayered styles in an `@layer` definition? `Initial` and `*` do not really make much sense to me as they already have a meaning in CSS. `Initial` being an initial value and I do not really think of unlayered styles as an initial value. When I see `*` it means it can be any or all things. Unlayered styles are something specific so the `*` does not really fit. I also don't really like the overrides options, it feels like adding important flags to a CSS rule.

This seems easy to read and understand. It goes from lowest to highest
```
@layer reset, theme, unlayered, blocks, user;
```

or 

```
@layer reset, theme, blocks, user, unlayered;
```

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


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

Received on Friday, 5 July 2024 16:21:08 UTC