-
Notifications
You must be signed in to change notification settings - Fork 53
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
removeparam
rule not being enforced
#140
Comments
Weird, it doesn't work in latest release, but it works when I compile a local version of uBOL. Now it works in the latest release, not sure what is going on. |
Still doesn't work for me. 🤷🏻♂️ |
Very weird... Re-enabling the basic or regional subscription helps me. VideoVideo_2024-06-21_231213.mp4 |
This comment was marked as abuse.
This comment was marked as abuse.
removeparam
rule no tbeing enforcedremoveparam
rule not being enforced
@garry-ut99 Thanks for the investigation, I confirm there is an issue with how the DNR rule works. Simple repro steps is to take two generic
Probably related webextensions issue: w3c/webextensions#468 |
Hello, I'm working on an MV3 extension project to remove nasty tracking parameters from URLs. I've encountered an issue with DNR (Declarative Net Request) limitations: DNR claims:
But from my research, there's a hidden limit:
Real example:
Solution: |
So in short before you reached 30000 limit you exaused 50 ruleset limit |
@gorhill I see a case where the removed parameters left STR:
In the network console, I see Is it an issue from MV3 itself? |
Related issue: uBlockOrigin/uBOL-home#140 This will allow more specific `removeparam` filters to override generic ones. This doesn't fix the related issue but should help more specific `removeparam` filters to be applied. Related webextensions issue: w3c/webextensions#468
Google Chrome
uBlock Origin Lite 2024.6.17.766
Does this rule not work due to MV3 limitations?
*$removeparam=xtor
~> AdGuard URL Tracking ProtectionThe text was updated successfully, but these errors were encountered: