- From: Riad Benguella via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jul 2024 07:18:11 +0000
- To: public-css-archive@w3.org
I've been watching this issue for some time, and I'm failing to see how the `!overrides` solution address our use case in WordPress. Let me share some context. For a WordPress, We have a number of implicit layers today that are mostly definited using specificity. - Reset Layer - Theme Styles Layer - Block Styles Layer (provided by Core and Plugins) - User Styles Layer Also plugin authors can inject random CSS where we don't really know which layer the layer. We would like to explore CSS layers but there's a strong backward compatibility policy which prevents us from doing any breaking change. We think that the unlayered styles that we basically don't control (so can't change them at all) should probably go between "theme" and "block styles" or potentially between "block styles" and "user layer" which means that there are potentially two to three layers that should precede the "unlayered" layer. How do you think this could be handled. -- GitHub Notification of comment by youknowriad Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-2208282729 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 July 2024 07:18:11 UTC