-
Notifications
You must be signed in to change notification settings - Fork 7
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
Provide an option to block request when it's opened in the main frame #152
Comments
@ameshkov thanks for approving my idea. Regards |
@FadeMind it makes perfect sense, thank you! Also, it's quite often when people ask us how to block this or that completely, and using |
core/pull-requests/1482 |
core/pull-requests/1564 |
Regarding this issue - #152 (comment) It seems that it happens again. Steps to reproduce:
Request marked as |
It's not a regression since the actual request type detected by the filtering engine is xhr+document. |
Ok, thank you for your answer. |
@AdamWr, as for Adg4Win we'll improve content-type displaying soon - the corresponding task has been created |
Details:
AdguardTeam/AdguardForWindows#2043
Basically, we need to provide a "strict" level of blocking. When the strict level is enabled, we should block requests even when they're executed in the main browser frame.
Also, we'd better provide a modifier for blocking rules that will allow overriding the default behavior:
AdguardTeam/AdguardForWindows#2084 (comment)
The easiest way would be to allow
$document
modifier in the blacklist rules.Also, add
$all
modifier:https://github.com/gorhill/ublock/wiki/Static-filter-syntax#all
The text was updated successfully, but these errors were encountered: