You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe how CSS4 ':has()' handled in browsers without it's support (old Safari, Firefox without experimental flags), including cases where the selector is not supported by CSS4 (:has(:contains(aaa)));
in which cases native implementation may fail to hide an element;
performance comparison.
The text was updated successfully, but these errors were encountered:
Sure this thread OP is more than 3 months old by now, but things have picked up very fast after Eyeo sent out an E-mail some days ago to its related filterlist makers that strongly and honestly very suddenly recommended switching from #?# + :has, to ## + :has (except if the entry also has :has-text), the logic being that Firefox Stable (and presumably also Beta and Nightly) added native CSS :has in early December 2023.
I had already converted all of my own lists to ##, but realised regarding EasyList Lithuania and Adblock List for Finland (finnish-easylist-addition/finnish-easylist-addition#450 (comment)), "Wait, hold on the horses a little bit. To which extent would this new syntax affect Firefox ESR and quite a few browsers that are forked from ESR (Tor Browser being the biggest example IIRC), which'd seemingly be quite substantially for Browser Extension; and/or should adblockers even accomodate to ESR at all?"
So, this is certainly a good time to consider relatively fast what to do with this situation.
:has(:contains(aaa))
);The text was updated successfully, but these errors were encountered: