4 ms·

I was neither sharing an opinion nor did I claim anything. I asked OP to elaborate and referred them to content of the article. > You know why it never happene

by uallo 4y ago

I was neither sharing an opinion nor did I claim anything. I asked OP to elaborate and referred them to content of the article. > You know why it never happened? Yes, I do. > Especially when all we have is their word. Does that mean you don't trust their word? Good. Would you trust their own benchmark? No? The parent selector has been in Safari 15.4 since March, 2022. So feel free to do your own benchmark. There is not just their word. You might also find the lengthy explainer of Igalia, where performance is discussed, interesting: https://github.com/Igalia/explainers/tree/main/css/has https://github.com/Igalia/explainers/tree/main/css/has Being skeptic is not a bad thing. But (uninformed) criticism without any specifics is far from "well founded skepticism". JavaScript interpreters used to be very slow twenty years ago, now they are extremely fast. That can happen to CSS evaluation, too.

oblak 4y ago
March 2022 you say? Great. Are there any benchmarks? Nothing fancy, just some 3rd party comparisons to other selectors or combinations. Because that would be preferable to buying myself a safari capable device just to prove point that I wasn't making in the first place
- uallo 4y ago
  I'm not aware of any benchmarks. Neither am I aware of any performance deterioration in Safari 15.4+. What is your point exactly? That performance should be one of the most important aspects in browser engine development? I agree. Hence, I asked OP to elaborate their claim that this selector harms slow devices. And I'm not interested in the (outdated?) historical concerns of a parent selector. But the actual effect of the specific selector implementation in WebKit which this discussion is about.