A lot of the comments on the post about :has complain that browsers haven't implemented it yet. The reason it hasn't been implemented is (probably) that it's a

A lot of the comments on the post about :has complain that browsers haven't implemented it yet. The reason it hasn't been implemented is (probably) that it's a big perf footgun (not because of laziness). It essentially doubles the amount of work you need to do in applying the cascade. I suspect some browsers implement it internally anyway, but leave it off for web content. I don't remember the exact circumstances, but a month ago we were discussing some optimizations in Servo (which has parallel styling, making `:has` even worse), and often my thoughts would be "thank god :has doesn't exist", because it would often destroy the premise of the optimization. I'm sure that optimizations can be done so that pages without :has are unaffected and pages with :has aren't affected as much, but how much is enough? So I'm skeptical if it will ever make it. I'm not involved in the discussions here so I don't know what the current status is. I mean, I've often felt the need for :has. I wish we could have it. I'm not sure if it's a good idea taking perf into consideration.