-
Notifications
You must be signed in to change notification settings - Fork 802
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
Not an issue : how to disable a 3rd-party filter? #23
Comments
Currently exception filters such as |
OK, gorhill, thanks. Toggling off cosmetic filtering for the site has the inconvenience of being exaggeratedly radical and the advantage of immediate efficiency. Of course it's bothering to lose other wished cosmetic filters applicable to the site for the sake of disabling only one. Anyway I know now how to proceed. |
Is there an issue with |
There's always an issue with DailyMotion, not with UBO scripts which handle the issues correctly but which may face a site's obsession to continuously modify their code to perform, in the case of DailyMotion, their in-video ad force-feed. Confronted recently to a non efficiency of That's the trigger for this post, and an example as well to ask for the exception filters availability. But the trigger was DailyMotion. The video company doesn't yet haunt my nightmares but not far. What a pain... Sorry, unable to make it short, not in my genes :) |
At the same time, the following issues were fixed: - #1954: automatically lookup site-specific scriptlets - uBlockOrigin/uAssets#23
Fixed with gorhill/uBlock@a7fe367.
or for a specific site:
|
Good to know, thanks for pointing it out, gorhill |
Just a fast, easy question regarding a point I should know by the time but ignore nevertheless:
How must I proceed to disable a given 3rd-party filter?
Specifically, I wish to disable 3rd-party filters / uBlock filters / dailymotion.com##script:inject(1136.js)
I've tried adding to My filters, @@||dailymotion.com##script:inject(1136.js) but it doesn't seem to work.
Thanks
The text was updated successfully, but these errors were encountered: