- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Jan 2022 22:46:39 +0000
- To: public-css-archive@w3.org
I’d be fine with these limitations for `:has()` in L4 if it helps all browsers implement it sooner. It’s still infinitely better than restricting it to scripting only, as it was proposed earlier. To me, even limiting the argument to one combinator plus one compound selector (instead of arbitrary complex selectors) would be way better than nothing for many practical cases, and if it would allow to get rid of the “optional” status of `:has()` in the spec, I would accept that trade-off. Further extensions and improvements of this selector could be deferred to L5. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6952#issuecomment-1013524305 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 January 2022 22:46:40 UTC