Are :matches-path() and ::after supposed to work together ?

[Procyon-b]

I don't want to file a bug for this. Only a FYI if the limitation isn't intended.

I've solved an issue where, on a subreddit on old, the hover effect on the post downvote icon displays the ::after pseudo-element.

The filter old.reddit.com,www.reddit.com##div.arrow.down:hover::after works as expected.

I also wanted to limit the filter to that specific sub-reddit :
old.reddit.com,www.reddit.com##:matches-path(/r/CFB) div.arrow.down:hover::after
but apparently :matches-path() and ::after aren't allowed together.

Edit: uBO v1.60.1b15

[gorhill]

CSS pseudo elements can't be used with procedural cosmetic filters because querySelectorAll() doesn't work with these. MDN documentation:

CSS pseudo-elements will never return any elements, as specified in the Selectors API

[Procyon-b]

for me, both old.reddit.com,www.reddit.com##:matches-path(/r/CFB) div.arrow.down:hover
and old.reddit.com,www.reddit.com##div.arrow.down:hover work
But there is a race condition for the first. It's slower to take effect.

In fact the pure css filter is in itself an infinite loop:

• hide the element when mouse is over it
• element is hidden, mouse is not considered over it anymore, -> show the element
• the element is visible, mouse is over it -> hide the element
• etc...

browsers get out of the loop by ignoring step 3 if the mouse doesn't move.

[Procyon-b]

I suspected that it was caused by the implementation of :matches-path (hence, not a bug report).

[Procyon-b]

In my mind I don't consider :matches-path as a procedural filter similar to the others.
I'm too stylus-inclined. ;)

[krystian3w]

#3235 (comment) gorhill/uBlock@8b696a6

If page is static (lack of dynamic JS changes or updating uri in JS).