malhuda/AdguardKnowledgeBase
1
0
Fork 0
mirror of https://github.com/AdguardTeam/AdguardKnowledgeBase.git synced 2025-02-20 11:13:10 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

changed wording of one sentence

Browse Source
This commit is contained in:
Anastasiia Fedotova 2021-11-19 10:24:11 +03:00
parent bfaf6576f3
commit 53087b4bf5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
01.general/02.how-to-create-your-own-ad-filters/docs.en.md
View File

@ -434,7 +434,7 @@ The rule corresponds to the main frame document requests, i.e. HTML documents th
By default, AdGuard won't block the requests that are loaded in the browser tab (e.g. "main frame bypass"). The idea is not to prevent pages from loading as the user clearly indicated that they want this page to be loaded. However, if the `$document` modifier is specified explicitly, AdGuard does not use that logic and prevents the page load. Instead, it responds with a "blocking page".
If this modifier is used with an exclusion rule (`@@`), it completely disables blocking on corresponding pages. It is equal to the simultaneous use of `$elemhide`, `$content`, `$urlblock`, `$jsinject` and, `$extension` modifiers.
If this modifier is used with an exclusion rule (`@@`), it completely disables blocking on corresponding pages. It is equivalent to using `$elemhide`, `$content`, `$urlblock`, `$jsinject`, and `$extension` modifiers simultaneously.
> **Compatibility with different versions of AdGuard.** Blocking request type logic now only supported by dev-build of AdGuard.