- From: Michał Gołębiowski-Owczarek via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Sep 2022 16:49:10 +0000
- To: public-css-archive@w3.org
@emilio
> Shouldn't jQuery check `CSS.supports("selector(:has(....))")`, which should be unforgiving per spec? See #7280
In Chrome 105, `CSS.supports('selector(:has(div:contains(div)))')` returns `true`. I'd gladly use this in jQuery if this was working as advertised.
> Also, is this a "recent version of jQuery" kinda thing? Or would this change cause issues on older jQuery versions?
As I wrote in https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1235358708, this affects virtually all jQuery versions used in the wild.
> Is there any real-world site broken by the change? How frequent do we expect it to be to use jQuery-specific selectors inside `:has()` to begin with?
I am unable to answer this question. But it did both break our test suite and get us a report from a user at https://github.com/jquery/jquery/issues/5098. @Rinzwind did you encounter this issue just in manual testing or did it actually break anything for you on a live site?
--
GitHub Notification of comment by mgol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1235714917 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 September 2022 16:49:12 UTC