-
Notifications
You must be signed in to change notification settings - Fork 728
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
body:style breaks cosmetic filters #438
Comments
This filter is not valid for two reasons:
See https://github.com/gorhill/uBlock/wiki/Static-filter-syntax#style. |
Another issue, is that even with a valid cosmetic filter, the page removes all of uBO's injected styles. This sort of behavior was reported here. In such case, use Firefox, it does support real user styles. |
This also works as far as I can tell:
|
You'r great! Thank you for detailed response! With your code i don't even need add to Tampermonkey 'RU Adlist JS Fixes' |
I think some functionality are broken on some pages though. Using Firefox is the best fix though, Chromium-based browsers do not support user styles yet, it might even take a while before they do. |
URL(s) where the issue occurs
https://kurs.com.ua/novost/21233-na-valjutnom-rinke-perelom-trenda/
But it can be everywhere where is cosmetic filters apply
Describe the issue
I can't fully say that this is issue of uBlock or my misunderstanding but when in 'My Filters' i use this '##body:style(background-image: url() !important; overflow: auto !important;)' cosmetic filters are not applied. But when i open logger and from it refresh page cosmetics applies with some delay. Also sometimes it need second refresh to apply or "unaplly".
Screenshot(s)
As i think screenshot will not describe problem truly. Video will be better (if needed)?
Versions
Settings
Settings:
3d-party filters:
My filters:
Notes
As i pointed in description i tried catch this "bug" in logger but no luck. Maybe i not clearly understand how to use cosmetic filters with explicit style properties?
The text was updated successfully, but these errors were encountered: