Skip to content

Commit

Permalink
Update docs/general/ad-filtering/create-own-filters.md
Browse files Browse the repository at this point in the history
Co-authored-by: Helen <58733007+el-termikael@users.noreply.github.com>
  • Loading branch information
105th and el-termikael authored Aug 2, 2023
1 parent 3d03b9f commit bf8b347
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/general/ad-filtering/create-own-filters.md
Original file line number Diff line number Diff line change
Expand Up @@ -608,7 +608,7 @@ The rule corresponds to the main frame document requests, i.e. HTML documents th

By default, AdGuard does not 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 equivalent to using `$elemhide`, `$content`, `$urlblock`, `$jsinject`, `$extension` modifiers simultaneously but only if this modifier is written in the rule and not added hidden, for example in rule `@@example.com$removeheader` which implicitly adds `$document`.
When used with an exclusion rule (`@@`), this modifier completely disables blocking on the corresponding pages. It is equivalent to using the `$elemhide`, `$content`, `$urlblock`, `$jsinject`, `$extension` modifiers simultaneously, but only if this modifier is written in the rule and not added hidden, for example in the rule `@@example.com$removeheader`, which implicitly adds `$document`.

**Examples**

Expand Down

0 comments on commit bf8b347

Please sign in to comment.