- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Nov 2023 18:16:59 +0000
- To: public-css-archive@w3.org
Would this also help solve the use-case of a site refactor, or transition to using layers? The process I imagine would be something like importing a new stylesheet into the 'override' layer, and working within that layer until the old styles can be removed. (tho I suppose that's not much different from importing the old styles into a less powerful layer) Is there potential for people to see this as a form of 'progressive enhancement' where broad defaults 'should' be un-layered for older browsers, and then more detailed styles are layered on top, and only work in modern browsers? Even if that happens, I suppose – with most styles written in the override layer - we still don't have the issues that came with defaulting unlayered styles least powerful. That approach meant the only way to override a third-party layer was to layer your own styles. But with this approach you can still nest third-party 'override' styles into a layer below your own un-layered styles. The 'override' behavior can be scoped like any other layer, and doesn't necessarily impact every other stylesheet. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-1806199922 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 November 2023 18:17:01 UTC