Logger reports generic cosmetic filter instead of a specific

[peace2000]

Prerequisites

• I verified that this is not a filter issue (MUST be reported at filter issue tracker)
• This is not a support issue or a question
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue
• The issue is not present after wholly disabling uBlock Origin ("uBO") in the browser
• I checked the documentation to understand that the issue I report is not a normal behavior

I tried to reproduce the issue when...

• uBO is the only extension
• uBO with default lists/settings
• using a new, unmodified browser profile

Description

If there's the same cosmetic filter as a generic and as a specific, the logger reports the generic being loaded instead of the specific, if the generic filter is listed before the specific filter in the filter list.

A specific URL where the issue occurs

elisaviihde.fi

Steps to Reproduce

1. Add these to your own filters manually, in this order:
   ##.ea-cookie-disclaimer
elisaviihde.fi##.ea-cookie-disclaimer
2. Activate logger
3. Go to elisaviihde.fi

In the logger, you'll see that the generic filter is reported instead of the specific.

If you change the order:

elisaviihde.fi##.ea-cookie-disclaimer
##.ea-cookie-disclaimer

Logger will report the specific one as it should.

Expected behavior

The logger would always report the specific filter over the generic as it was the purpose of this commit:

gorhill/uBlock@c25938f

Actual behavior

The logger reports a generic cosmetic filter over a specific one, if the generic filter is listed before the specific in the list.

uBlock Origin version

1.42.5b1

Browser name and version

Firefox 99.0.1

Operating System and version

Windows 10

[peace2000]

Did some digging.

1.39.2 is the last stable version where this works correctly.
1.40.0 doesn't work correctly since this version. Maybe this commit is related to the issue? gorhill/uBlock@72bb894

[gwarser]

@peace2000 is this fixed in 1.42.4? I cannot reproduce in Nightly.

[peace2000]

No, I can repro this issue in that version as well. 1.39.2 is the last stable version where this works correctly.

@gwarser

[gwarser]

Weird. It really must be related with sequence of data in storage, because no matter what I do, I cannot reproduce in dirty profile. I can in clean installation.

[gorhill]

Hypothesis: Could be a regression from gorhill/uBlock@72bb894.

[peace2000]

Tested the latest dev build, seems to be working.