- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jul 2023 21:17:54 +0000
- To: public-css-archive@w3.org
> And Chrome has _different_ timing if you collapse away the nesting. That is, `:is(a, b) { :is(c, d) {...}}` and `:is(a, b) :is(c, d) ... {...}` are at least a 10x difference in timing (with the 25 `:is()` functions, i got 0.8s vs 13s on my laptop). So it's still slow, but there's something else also contributing to the blowup.
That seems to indicate that there is a design choice in Chrome's implementation that is causing this to be an issue at levels lower than it could in theory. Maybe once that root cause is identified, it would be possible to agree on a very large limit and call it a day.
--
GitHub Notification of comment by FremyCompany
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2881#issuecomment-1642771347 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 July 2023 21:17:56 UTC