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
The issue is not present after disabling uBO in the browser.
I checked the documentation to understand that the issue I am reporting is not normal behavior.
I tried to reproduce the issue when...
uBO is the only extension.
uBO uses default lists and settings.
using a new, unmodified browser profile.
Description
We still keep these and bunch of specific cosmetic filters just for those who have been using uBO since before we enabled generic cosmetic filters by default on mobile:
Actually they are useful not only to mobile user, but to anyone who disabled generic cosmetics too. And now, if I understand correctly, uBOL does not apply generic cosmetic filters in Optimal mode. For all of them this directive will be useful.
A specific URL where the issue occurs.
E.g. https://github.com/uBlockOrigin/uAssets/issues/21924
Steps to Reproduce
NA
Expected behavior
NA
Actual behavior
NA
uBO version
1.62.0
Browser name and version
Chrome 134.0.6998.36
Operating System and version
Windows 11
The text was updated successfully, but these errors were encountered:
for those who have been using uBO since before we enabled generic cosmetic filters by default on mobile
I am pretty sure that when the setting was toggled off by default (March 2024), those who had uBO installed before would still benefit the change since uBO saves only the settings which differ from default state.
As for uBOL, I am confused about how this would help since the lists are compiled at extension building time: how would cap_generic_hiding be used and how would it help?
As for uBOL, I am confused about how this would help since the lists are compiled at extension building time: how would cap_generic_hiding be used and how would it help?
Woops, I forgot that. Maybe the value should be false for uBOL. The idea is to limit these filters only to needed congifuration and move from filters-mobile.txt, as they're valuable if you have "Ignore generic cosmetic filters" checked or for chose Optimal mode in uBOL, but not for others.
Prerequisites
I tried to reproduce the issue when...
Description
We still keep these and bunch of specific cosmetic filters just for those who have been using uBO since before we enabled generic cosmetic filters by default on mobile:
Actually they are useful not only to mobile user, but to anyone who disabled generic cosmetics too. And now, if I understand correctly, uBOL does not apply generic cosmetic filters in Optimal mode. For all of them this directive will be useful.
A specific URL where the issue occurs.
E.g. https://github.com/uBlockOrigin/uAssets/issues/21924
Steps to Reproduce
NA
Expected behavior
NA
Actual behavior
NA
uBO version
1.62.0
Browser name and version
Chrome 134.0.6998.36
Operating System and version
Windows 11
The text was updated successfully, but these errors were encountered: