- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Nov 2024 22:47:17 +0000
- To: public-css-archive@w3.org
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-transitions-2] Should @starting-style add a teensy bit of specifity? == See <https://youtu.be/DNXEORSk4GU?si=FaHmoCzBpQPF9eeS&t=1161> for context. In this video, the dev explains that they used to put `@starting-style` at the top of their rule, which felt more natural, but now that we've changed how Nesting works, that no longer works - the plain declarations are no longer shifted above the nested rules, so the `@starting-style` styles lose due to order-of-appearance. Instead, you have to put `@starting-style` below your other declarations. This feels like a frustrating footgun. Would it make sense to have `@starting-style` introduce a new, lowest bit of specificity, so it'll win over plain declarations in the same parent rule regardless of the order it appears in? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11263 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 November 2024 22:47:18 UTC