- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Jan 2023 12:20:33 +0000
- To: public-css-archive@w3.org
> (@anttijk) I wonder how many developers can correctly tell what `.c :is(.a .b)` actually matches. A quick informal ask around to a handful of devs I know didn’t realize it behaved as is behaves the way it does. They all thought it didn’t really make a difference and would act the same as `.a .b .c`. Simultaneously I received [this feedback from Ana Tudor](https://twitter.com/anatudor/status/1615606130096459777), a well respected voice within the developer community who’s known for pushing the capabilities of CSS to its limits: > I don't see the logic behind ever using `.a :is(.b .c)` (unless what you really want is to catch the `.b .a .c` case too), whether you manually write it like that or it's generated from the way you nest things. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8310#issuecomment-1386966144 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 January 2023 12:20:34 UTC