- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 17:08:59 +0000
- To: public-css-archive@w3.org
Won't option 3 just lead to the same kind of conflicts as we see with `!important`?
What I like about `@layer` is that the order of layers isn't fixed.
The "owner" of the page can intervene and always add a list of layer names in their preferred order at the top of their page. This is a really nice "conflict resolution" feature.
But with option 3 we would introduce a mechanic that again wins over everything.
A 3rd party could write all their styles in `@layer !important {}`, forcing any other styles sharing the same page to at least match that.
`@layer !important {}` would effectively become the new unlayered styles. So we wouldn't have solved the underlying issue, we would have just moved it around a bit :)
While with option 2 it we still leave the option open to place other layers before or after the "strong layers" that might be coming from other sources.
--
GitHub Notification of comment by romainmenke
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-2432893708 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 October 2024 17:09:00 UTC