- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Mar 2024 15:59:39 +0000
- To: public-css-archive@w3.org
In general, "special syntax to make something go first" isn't very composable. Things end up fighting over being first, the set of things putting themselves first still needs to establish a relative ordering. You just kick the bucket of "it's hard to coordinate" a little bit down the line, but not *very* far. On the other hand, we *have* had multiple proposals for something like `!default` as the inverse of `!important`, just a way to downgrade a style to be weaker than all "normal" styles. So this might indeed be reasonable, just establishing that there's a specific layer that's always defined and before all named layers. Some specific comments: * sublayers of this initial layer are absolutely required. Nothing about an initial layer negates the need for organizing styles within the layer. * I don't think named layers need an "initial" sublayer. By definition, you're in control of the named layer; you can set up your sublayer order immediately. The only possible concern is that someone else is using the same layer name and so you're fighting over the namespace, but that just means you should use a different name. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10094#issuecomment-2004316955 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 March 2024 15:59:40 UTC