- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Oct 2021 21:01:36 +0000
- To: public-css-archive@w3.org
> My concern here is that a layer (whether named or anonymous) that is not accounted for in the first statement that mentions initial has no way to pull itself ahead of the unlayered rules. Yes, but that's true of every other layer, too. If you have a `foo` layer early in the order, a later `bar` layer is unable to ever put itself before it unless it's explicitly named as such in a preceding `@layer bar, foo` rule. What's special about the initial layer such that it requires us to favor it here? Remember that the intention is that if you're using layers, ideally *all* your styles are layered so you have full control over the ordering; we need to handle the initial layer just to help with adapting an existing unlayered codebase into using layers. It's not *meant* to be special in any particular way otherwise. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-947101607 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 October 2021 21:01:38 UTC