Re: [csswg-drafts] [css-cascade] New syntax for making an entire layer important (#7535)

I the `@keyframes` issue can already be resolved using layers, without any need for importance. Naming conflicts between at-rules are already resolved using layer order.  Importance doesn't add much to that use-case.

For the OP use-case (injected user-styles not in the user stylesheet), that is the same use-case that lead to reopening #6323. We may only need one of these features, and not the other?

Beyond this specific use-case, I think it's generally better to keep styles grouped by their purpose rather than their importance. E.g. we should be putting `!important` on specific properties in the `component` layer block, rather than creating a new `component !important` block. Are there other use-cases where an entire group of styles really should be easily marked as important?

-- 
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7535#issuecomment-1850925063 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 11 December 2023 21:34:46 UTC