-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Domain-anchored filters that can't be tokenized, are rejected #1765
Comments
@gorhill The fix for this issue has caused a regression where uBlock Origin no longer rejects truly invalid filters such as
Steps-to-reproduce:
This is the error message uBlock Origin without this fix would give:
(I don't know if it's reasonable for uBlock Origin to distinguish invalid filters like this from valid-but-non-tokenizable filters like in the description, so if it comes down to that, personally I'd prefer to keep the fix.) |
A quick opinion: the filter should probably still be valid, but not parsed as |
Not sure how to find that out for sure. But I ran it through this function and got this regex:
Will that ever match any actual URLs? |
Describe the issue
Reporting this: https://forums.informaction.com/viewtopic.php?p=83403#p83403
Valid domain-anchored filters which can't be tokenized are being rejected as invalid by uBlock Origin.
Steps for anyone to reproduce the issue
new profile
Expected results: the filters are accepted by uBlock Origin, but are not very efficient, because as gorhill described, they would have to be checked against every network request.
Actual results: the filters are rejected as invalid, as indicated by these console messages:
(Workaround: specify such filters as regular expression instead)
Your settings
[mostly listed elsewhere]
new profile
about:config > xpinstall.signatures.required;false
Your filter lists
[none]
Your custom filters (if any)
The text was updated successfully, but these errors were encountered: