Re:Is Chrome the New IE?
by sureIy on Monday November 18, 2024 @11:38PM
(#42180131)
Safari was late until a couple of years ago when they started implementing new features more aggressively. Now it's always Firefox. Just check how long it took them to add support for the :has() selector and RegEx Lookbehind. We're years into "manifest v3" and background workers are nowhere to be found.
[ Parent
| on HN ]
Funnily enough it was Firefox who figured out a workable algorithm for :has IIRC
Absolutely not.
Firefox has mindbogglingly bad performance with :has() even if their superficial tests tell you otherwise. I experienced minute-long lockups just because I used :has() on a large element like body. Chrome and Safari had no issues with those selectors.
I stand corrected. It was the absolute legends at Igalia. See links and explainer here: https://github.com/mozilla/standards-positions/issues/528