- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Sun, 16 Nov 2025 00:51:44 +0000
- To: public-css-archive@w3.org
@SebastianZ yeah, I guess the main question is: This has never mattered before, is that what we want? There are also pseudo selectors (view-transition-classes etc) which add their own specificity on top. > authors should have the option to remove the pseudo-selector specificity using :where() Note that we resolved on the other issue that `:is()` / `:where()` would keep _not_ working, this was a nesting-specific change. So I don't think that works... -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13108#issuecomment-3537217227 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 16 November 2025 00:51:45 UTC