Update docs

This commit is contained in:
Florian Bruhin 2018-10-05 23:42:28 +02:00
parent c6dc9206e6
commit 5fd20da915
3 changed files with 11 additions and 0 deletions

View File

@ -38,6 +38,8 @@ Changed
- The `QtColor` config type now also understands colors like `rgb(...)`.
- `:yank` now has a `--quiet` option which causes it to not display a message.
- The `:open` completion now also shows search engines by default.
- The `content.host_blocking.enabled` setting now supports URL patterns, so the
adblocker can be disabled on a given page.
Fixed
~~~~~

View File

@ -1738,6 +1738,8 @@ Default: empty
=== content.host_blocking.enabled
Enable host blocking.
This setting supports URL patterns.
Type: <<types,Bool>>
Default: +pass:[true]+
@ -1768,6 +1770,7 @@ Default:
[[content.host_blocking.whitelist]]
=== content.host_blocking.whitelist
A list of patterns that should always be loaded, despite being ad-blocked.
Note this whitelists blocked hosts, not first-party URLs. As an example, if `example.org` loads an ad from `ads.example.org`, the whitelisted host should be `ads.example.org`. If you want to disable the adblocker on a given page, use the `content.host_blocking.enabled` setting with a URL pattern instead.
Local domains are always exempt from hostblocking.
Type: <<types,List of UrlPattern>>

View File

@ -565,6 +565,12 @@ content.host_blocking.whitelist:
desc: >-
A list of patterns that should always be loaded, despite being ad-blocked.
Note this whitelists blocked hosts, not first-party URLs. As an example, if
`example.org` loads an ad from `ads.example.org`, the whitelisted host
should be `ads.example.org`. If you want to disable the adblocker on a
given page, use the `content.host_blocking.enabled` setting with a URL
pattern instead.
Local domains are always exempt from hostblocking.
content.hyperlink_auditing: