4 ms·

I'd add Firefox to that list; specifically, you shouldn't be using :has until Firefox implements it, and afaik it's not implemented in Firefox because it's stil

I'd add Firefox to that list; specifically, you shouldn't be using :has until Firefox implements it, and afaik it's not implemented in Firefox because it's still a Working Draft and not finalized. Chrome and Safari implemented it early, and without any vendor prefix, but the implementation details are still subject to change. (Someone correct me if I'm wrong.)

Dalewyn 3y ago
>you shouldn't be using :has until Firefox implements it, 97.23% of internet users do not care. If you are arguing to not use Working Draft mechanisms in production environments (and you probably are), yes you have a point. Better safe than sorry, it's called a Working Draft for a reason. But if you are arguing to not use something because Firefox (and only Firefox) does not support it, you are going to have a fun time trying to convince most webdevs to care about just 2.77% of all internet users.