W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2021

Re: [csswg-drafts] [css-cascade-5] Any needs to avoid other layers overriding name-defining @-rules? (#6461)

From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Jul 2021 16:25:30 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-883527162-1626798328-sysbot+gh@w3.org>
I don't see this as an issue specific to cascade layers, or one that layers need to solve. It is already possible for name-defining rules to override each other, and layers make it simpler to describe the _order_ in which they override each other. If the override is intentional, then layers are working as designed. If the override is _accidental_, then it's not a new problem specific to layering. It seems more like a namespace/scope issue.

- If we want to add `!important` at-rules, I think that's an interesting idea, but somewhat tangential to this feature. 
- I would not like to add layer-scoped names. I think that approach blurs the goals. Layers are not a mechanism for locking in particular references to avoid conflicts (that's a scope issue), they are a mechanism for clearly defining an order of cascade precedence – which is working successfully in the example. Authors can move their animations into the appropriate layers so that the proper one is applied.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 July 2021 16:25:38 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:39 UTC