Skip to content
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

Closed
ghost opened this issue Apr 21, 2016 · 6 comments
Closed

Not an issue : how to disable a 3rd-party filter? #23

ghost opened this issue Apr 21, 2016 · 6 comments

Comments

@ghost
Copy link

ghost commented Apr 21, 2016

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

@gorhill
Copy link
Member

gorhill commented Apr 21, 2016

Currently exception filters such as [...]#@#script:[...] are not supported. However, if you toggle off cosmetic filtering for the site, scriptlets won't be injected.

@ghost
Copy link
Author

ghost commented Apr 21, 2016

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.
This was not an issue stricto sensus , but where else to expose a non-issue question? If there is thanks for letting me know.

@gorhill
Copy link
Member

gorhill commented Apr 21, 2016

Is there an issue with script:inject(1136.js)?

@ghost
Copy link
Author

ghost commented Apr 21, 2016

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 script:inject(1136.js) to block what appeared to be another code shift on the part of DailyMotion I just started wondering if it wouldn't be more pertinent -- as far as I'm concerned -- to consider another approach than that of a valuable script but vulnerable confronted to DailyMotion's ever-changing code : slightly annoyed of this continuous cat-mouse race, for me, for exposing it again & again, having you, gorhill, spend time modifying the script ... ouf! ... I ran into a userscript over at Greasefork which that simply replaces DailyMotions's (html5) video player with "pure" html5, I mean Firefox's built-in html5 video player -> no ads, whatever dailyMotion's excentricities.

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 :)

gorhill added a commit to gorhill/uBlock that referenced this issue Sep 12, 2016
At the same time, the following issues were fixed:
- #1954: automatically lookup site-specific scriptlets
- uBlockOrigin/uAssets#23
@gorhill
Copy link
Member

gorhill commented Sep 12, 2016

Fixed with gorhill/uBlock@a7fe367.

script:inject filters can now be "excepted" like any other cosmetic filters. Using the current issue, this would be:

#@#script:inject(1136.js)

or for a specific site:

dailymotion.com#@#script:inject(1136.js)

@gorhill gorhill closed this as completed Sep 12, 2016
@ghost
Copy link
Author

ghost commented Sep 12, 2016

Good to know, thanks for pointing it out, gorhill

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant