- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Jun 2023 05:41:25 +0000
- To: public-css-archive@w3.org
> While in theory we could detect and optimize some very specific cases of `:has()` such as `:has(:target)`, that seems like it would create more confusion around what the performance characteristics of CSS selectors are. There's value in creating a platform that is understandable to the developers that use it -- and this does apply to its performance characteristics. There is definitely value in creating a platform that is understandable to the developers that use it; however my understanding was that one of the core design principles of CSS these days is that authors should not need to worry about performance at all; if something cannot be implemented performantly, it's not implemented at all. Is this not the case with `:has()`? I thought the whole reason `:has()` became feasible was that it was shown it could be implemented with reasonable performance. Is this not the case? -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8357#issuecomment-1590504998 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 June 2023 05:41:26 UTC