- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Oct 2021 22:24:33 +0000
- To: public-css-archive@w3.org
I'm not a big of this "two lists" idea - it makes ordering less obvious (no longer order-of-appearance, but two simultaneously-calculated orders of appearance), and it brings up identity questions like what @FremyCompany referenced without good answers.
"One-off" layers that are before/after a specific significant layer are already something authors might want for *any* layer, but we don't allow that because it's *better* for the page to declare its layer order up-front; it makes the entire feature more understandable and manageable over time. I don't think the default layer is in any different in this respect.
(We *do* at least let styles arbitrarily inject themselves after a given layer via nesting; an `@layer foo.bar{...}` comes after all the "foo" layer styles. We could allow nesting under `initial` (assuming that's what we call the default layer) to let people achieve *some* of this, in a way that's consistent with any other layer.)
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-939147623 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 October 2021 22:24:35 UTC