Add env_ubol directive

[Yuki2718]

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

We will eventually need this directive as uBOL is simply too different. For example, uBlock filters heavily rely on look-ahead regex to catch revolving adservers, which is not possible under MV3. In that case we may need to add a denyallow or scriptlet rule just for uBOL (denyallow is risky so should be avoided if not needed thx to the regex, but in MV3 world there won't be many option). Here an actual case on www.animefenix.org as of now - due to revolving nature of these adservers it will change - with uBO proper there's no problem thx to a rule /^https?:\/\/(?:[a-z]{2}\.)?[0-9a-z]{7,16}\.com\/[a-z](?=[a-z]{0,25}[0-9A-Z])[0-9a-zA-Z]{3,26}\/(?:[1-5]\d{4}|[3-9]\d{3})\??(?:_=\d+|v=\d)?$/$script,3p,match-case but with uBOL any click leads to:

Screenshot

Such cases are already common place for Safari content blocker whose regex support is even more ristricted than Chromium MV3 on AG repo. So I also propose to prepare a dedicated list for uBOL, just like the list for legacy or AG's Safari filter. Whether to use the new list or the directive will be determined by case by case basis.

And tho this is off-topic, I propose to set Quick fixes dynamic filter list on uBOL - it's pointless to have this list updated only on extension update.

A specific URL where the issue occurs

https://www.animefenix.org/

Steps to Reproduce

1. Visit the site with uBO proper and uBOL.
2. You may see popup only in uBOL. If not, there are plenty of other URLs to test I can post.

Expected behavior

We have a way to specifically address uBOL-specific issues.

Actual behavior

Curretnly not

uBlock Origin version

uBlock Origin Lite 0.1.22.9138

Browser name and version

Brave 1.43.93 with Shield turned off

Operating System and version

Windows 10

[gorhill]

I was planning to add env_mv3. I will add env_ubol instead to differentiate with other mv3 blockers which might have different capabilities.

On a related matter, I have been hesitant to add the support button in the popup panel, because given the current state of uBOL, I fear this would burden volunteers with too many reports which can't be solved at the moment given the limited capabilities, which I am working on expending.

[Yuki2718]

Regarding the new list, I completely forgot about the traffic argument. It's not needed soon.

[sillyjaybird]

Can you add a new label referencing UBOL specifically, so users may ID pertinent issues?

[Yuki2718]

env_mv3 may possibly be useful if there's something common in and specific to MV3 extension. @ameshkov Will you add specific directive for MV3 extension, or will just use adguard_ext_chromium even though Brave is likely to support MV2 extension?

[ameshkov]

@Yuki2718 good idea, we'll support this.

[Yuki2718]

Will ext_ublock value be false on uBOL?

[gorhill]

ext_ublock will evaluate to true, the goal is to support as much as possible all of uBO's filtering syntax.

[gorhill]

Supported in latest versions of both uBO and uBOL.

[Yuki2718]

@gorhill @ameshkov Can you please cordinate for something I can use in AG filters to specify MV3 environment (AGMV3 & uBOL)? IDK what is the best way, maybe env_mv3 and let it be passed to uBO version of AG lists (and then uBO/uBOL interprets this), or compile uBOL version of lists separately.