diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md
index 0e51ab28b05..5f5daea4453 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md
@@ -137,10 +137,10 @@ Pokud je toto nastavení povoleno, bude AdGuard filtrovat kromě jiných typů p
**O HTTP/3**: Jedná se o nejnovější verzi protokolu HTTP založenou na protokolu QUIC.
-**Limitations**:
+**Omezení**:
- Prohlížeče založené na Chrome nepřijímají uživatelské certifikáty, proto v nich není podporováno filtrování HTTP/3.
-- Firefox-based browsers behave similarly by default, but you can set the `network.http.http3.disable_when_third_party_roots_found` option in `about:config` to `false` to allow user certificates for HTTP/3.
+- Prohlížeče založené na Firefoxu se ve výchozím nastavení chovají podobně, ale můžete nastavit možnost `network.http.http3.disable_when_third_party_roots_found` v `about:config` na `false`, aby byly povoleny uživatelské certifikáty pro HTTP/3.
- Safari podporuje filtrování HTTP/3 bez další konfigurace.
### Odchozí proxy
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md
index df51df23e3d..c795ac4456f 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md
@@ -145,8 +145,8 @@ Upozorňujeme, že filtrování DNS bude aktivní i v režimu _Automatického pr
V této sekci najdete informace o své licenci a můžete provádět následující:
- Zakoupit licenci AdGuardu pro aktivaci [funkcí plné verze](/adguard-for-android/features/free-vs-full)
-- Log in to your AdGuard account or enter the activation code to activate your license
-- Sign up to activate your 14-day trial period. The activation code can be used on different devices and platforms
+- Přihlásit se ke svému AdGuard účtu nebo zadat licenční klíč pro aktivaci licence
+- Zaregistrujte se a aktivujte si 14denní zkušební období. Aktivační kód lze použít na různých zařízeních a platformách
- Obnovit stav licence z nabídky se třemi tečkami (⋮)
- Otevřít AdGuard účet a spravovat v něm své licence
- Resetovat licenci — například pokud jste dosáhli limitu zařízení pro tuto licenci a chcete použít jinou
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index f2a9e7b14ad..db1ad1508cd 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ Na zařízeních s uživatelským rozhraním Realme UI 4.0 existují tři klíč
- Vyhledejte **AdGuard** a povolte možnost **Always-on VPN**
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Přejděte na **Nastavení**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index c72b634c91c..9cf06eea99d 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard pro Linux vyžaduje [licenci AdGuardu](https://adguard.com/license.html)
2. Poté vyberte požadovanou možnost:
- 
+ 
3. Po získání licence pokračujte v aktivaci pomocí poskytnutého odkazu:
- 
+ 
4. Po aktivaci můžete s programem dále pracovat:
- 
+ 
5. Licenci můžete obnovit také zadáním:
@@ -77,7 +77,7 @@ AdGuard pro Linux vyžaduje [licenci AdGuardu](https://adguard.com/license.html)
adguard-cli configure
```
- 
+ 
Průvodce se zeptá na základní otázky potřebné pro počáteční nastavení.
@@ -87,7 +87,7 @@ AdGuard pro Linux vyžaduje [licenci AdGuardu](https://adguard.com/license.html)
adguard-cli start
```
- 
+ 
8. Stav ochrany můžete zkontrolovat pomocí:
@@ -101,7 +101,7 @@ AdGuard pro Linux vyžaduje [licenci AdGuardu](https://adguard.com/license.html)
adguard-cli stop
```
- 
+ 
9. Chcete-li zkontrolovat aktuální konfiguraci, zadejte:
@@ -109,7 +109,7 @@ AdGuard pro Linux vyžaduje [licenci AdGuardu](https://adguard.com/license.html)
adguard-cli config show
```
- 
+ 
Zobrazí se také cesta ke konfiguračnímu souboru, který můžete a měli byste přímo upravit. Obsahuje popisy všech dalších možností.
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md
index d2aabfde1be..0bcd5d77fc3 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md
@@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro macOS, multifunkční blokátor reklam, kter
:::
-## Features
+## Funkce
Hlavní funkce a nastavení dostupné v aplikaci AdGuard pro macOS
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/adguard-for-safari.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/adguard-for-safari.md
index 0e711705264..c46c911eeab 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/adguard-for-safari.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/adguard-for-safari.md
@@ -9,7 +9,7 @@ Tento článek je o AdGuardu pro Safari, který chrání pouze váš prohlíže
:::
-## Features
+## Funkce
Hlavní funkce a nastavení dostupné v aplikaci AdGuard pro Safari
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md
index d4d77504bab..ae6cef5dec9 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md
@@ -1,5 +1,5 @@
---
-title: Features
+title: Funkce
sidebar_position: 1
---
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md
index ae53f7257fa..ef23f5cb529 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md
@@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt
:::
-## Features
+## Funkce
Hlavní funkce a nastavení dostupné v aplikaci AdGuard pro Windows
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md
index 12134e13672..65811e5d05e 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md
@@ -1,5 +1,5 @@
---
-title: Features
+title: Funkce
sidebar_position: 1
---
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md
index f92346b3f59..0be61d0c1fa 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md
@@ -11,13 +11,13 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt
_Nastavení_ je část, která vyžaduje největší pozornost. Zde můžete program nakonfigurovat tak, aby plně vyhovoval vašim požadavkům: blokujte pouze to, co vám vadí, používejte DNS server důvěryhodného poskytovatele, odstraňujte soubory cookies třetích stran atd.
-### General settings
+### Obecná nastavení
-Here you can set the language and theme (Dark or Light), enable AdGuard launching at system start-up and silent automatic updates, choose the update channel and filter update check interval. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md).
+Zde můžete nastavit jazyk a motiv (tmavý nebo světlý), povolit spouštění AdGuardu při startu systému a tiché automatické aktualizace, vybrat aktualizační kanál a interval kontroly aktualizací filtrů. Pokud AdGuard pro Windows nefunguje správně a tým podpory vás požádal, abyste [shromáždili _Protokoly ladění_](/adguard-for-windows/solving-problems/adguard-logs.md), přejděte do Nastavení.
-At the very bottom of the screen you will find _Advanced Settings_. Changing some of them mindlessly may potentially cause problems with AdGuard’s performance, break the Internet connection or compromise your security and privacy. That’s why we suggest you open this section only if you are sure of what you are doing or our support team has asked you about it. If you want to know what can be set up in _Advanced Settings_, read the [dedicated article](/adguard-for-windows/solving-problems/low-level-settings.md).
+Úplně dole na obrazovce najdete _Pokročilá nastavení_. Bezmyšlenkovitá změna některých z nich může potenciálně způsobit problémy s výkonem AdGuardu, přerušit internetové připojení nebo ohrozit vaši bezpečnost a soukromí. Tuto část byste měli otevřít pouze v případě, že jste si jisti tím, co děláte, nebo pokud se vás na to zeptal náš tým podpory. Pokud chcete vědět, co lze nastavit v _Pokročilém nastavení_, přečtěte si [specializovaný článek](/adguard-for-windows/solving-problems/low-level-settings.md).
@@ -46,9 +46,9 @@ Mnoho webových stránek shromažďuje informace o svých návštěvnících, na
-You can flexibly adjust the work of _Tracking protection_: for instance, you can prohibit the website to receive the search request you used to find it on the Internet, automatically delete both third-party and website’s own cookies, and disable location sharing in your browser that can be used to track your whereabouts.
+Práci v _Ochraně před sledováním_ můžete flexibilně nastavit: můžete například zakázat, aby webová stránka obdržela požadavek na vyhledávání, který jste použili k jejímu nalezení na internetu, automaticky vymazat soubory cookies třetích stran i vlastní soubory cookies webové stránky a zakázat sdílení polohy ve vašem prohlížeči, které lze použít ke sledování vaší polohy.
-To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode).
+Chcete-li se dozvědět vše o _Ochraně před sledováním_ a mnoha možnostech, přečtěte si [tento článek](/general/stealth-mode).
### Bezpečné prohlížení
@@ -81,15 +81,15 @@ Od verze 7.20 můžete také přidávat filtry jednoduchým výběrem ze seznamu
-### Parental control
+### Rodičovská ochrana
-Existuje několik webových stránek, ke kterým by měl být omezen přístup z PC používaného dětmi. This task is accomplished by _Parental control_.
+Existuje několik webových stránek, ke kterým by měl být omezen přístup z PC používaného dětmi. Tento úkol zajišťuje _Rodičovská ochrana_.
-Modul kontroluje obsah webových stránek otevřených v prohlížeči a filtruje ty, jejichž obsah je pro děti nežádoucí: obrázky a texty pro dospělé, hrubý jazyk, násilí, propagace drog atd. Parental control settings are password-protected so that the child is not able to go round the restrictions. Tento modul nejenže blokuje vstup na nežádoucí stránky, ale také dokáže z výsledků vyhledávání odstranit odkazy, které jsou nevhodné pro děti.
+Modul kontroluje obsah webových stránek otevřených v prohlížeči a filtruje ty, jejichž obsah je pro děti nežádoucí: obrázky a texty pro dospělé, hrubý jazyk, násilí, propagace drog atd. Nastavení Rodičovské ochrany jsou zabezpečena heslem, takže dítě nemůže obejít omezení. Tento modul nejenže blokuje vstup na nežádoucí stránky, ale také dokáže z výsledků vyhledávání odstranit odkazy, které jsou nevhodné pro děti.
-In the _Parental control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Můžete také zaškrtnout políčko _Blokovat stahování spustitelných souborů_ a zabránit tak vašemu dítěti ve stahování a instalaci softwaru do PC. There are two more options in the _Parental control_ module: you can select a specific Windows user to be protected by _Parental control_ and set a password to protect AdGuard settings from change.
+V modulu _Rodičovská ochrana_ můžete povolit _Bezpečné vyhledávání_, spravovat _seznam zakázaných_, _seznam povolených_ a přizpůsobit si funkce těchto možností. Můžete také zaškrtnout políčko _Blokovat stahování spustitelných souborů_ a zabránit tak vašemu dítěti ve stahování a instalaci softwaru do PC. V modulu _Rodičovská ochrana_ jsou další dvě možnosti: můžete vybrat konkrétního uživatele Windows, který má být chráněn _Rodičovskou ochranou_ a nastavit heslo pro zabezpečení nastavení AdGuardu před změnami.
### Asistent prohlížeče
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index a7e2971dbd9..da4d92eb318 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Pravidla s modifikátorem `$popup` nejsou Blokátorem obsahu AdGuard podporován
Funguje stejně jako modifikátor [`$~third-party`](#third-party-modifier), ale zachází s požadavkem jako s vlastním, pokud má odkazovač a původ naprosto stejný název hostitele.
+Požadavky bez odkazovače jsou také považovány za vlastní požadavky a na tyto požadavky se vztahují pravidla s modifikátorem `$strict-first-party`.
+
**Příklady**
- domain.com$strict-first-party' – toto pravidlo platí pouze pro `domena.com`. Např. požadavek z `domain.com` na `http://domain.com/icon.ico` je požadavek vlastní. Požadavek z `sub.domain.com` na `http://domain.com/icon.ico` je považován za požadavek třetí strany (na rozdíl od modifikátoru `$~third-party`).
@@ -740,6 +742,8 @@ Místo plného názvu modifikátoru můžete použít kratší název (alias): `
Pravidla s modifikátorem `$strict-first-party` jsou podporována AdGuardem pro Windows, Mac, Android a Linux s [CoreLibs][] v1.16 nebo novější.
+Požadavky bez odkazovače jsou porovnávány podle pravidel s `$strict-first-party` v AdGuardu pro Windows, AdGuardu pro Mac a AdGuardu pro Android s [CoreLibs][] v1.18 nebo novější.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ Aby mohla být žádost třetí strany považována za takovou, měla by splňov
**`$third-party`:**
-- `||domain.com^$third-party` — toto pravidlo bude použito na všechny domény, kromě `domain.com` a její subdomény. Příklad požadavku třetí strany: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — toto pravidlo bude použito na všechny domény, kromě `domain.com` a její subdomény. Pravidlo se nikdy neuplatní, pokud neexistuje žádný odkazovač. Příklad požadavku třetí strany: `http://example.org/banner.jpg`.
-Pokud existuje modifikátor `$third-party`, pravidlo se použije pouze na požadavky, které nejsou od třetích stran. To znamená, že musí být odeslány ze stejné domény.
+Pokud existuje modifikátor `$third-party`, pravidlo se použije pouze na požadavky, které nejsou od třetích stran. To znamená, že musí být odeslány ze stejné domény nebo by neměly mít vůbec žádný odkazovač.
**`$~third-party`:**
-- `||domain.com$~third-party` — toto pravidlo se vztahuje výhradně na `domain.com`. Příklad požadavku která není podán třetí stranou: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — toto pravidlo se vztahuje výhradně na `domain.com`. Příklad požadavku která není podán třetí stranou: `http://sub.domain.com/icon.ico`.
+
+Požadavky bez odkazovače jsou rovněž považovány za požadavky, které nejsou požadavky třetích stran, a jsou na ně aplikována pravidla s modifikátorem `$~third-party`.
:::note
@@ -793,6 +799,12 @@ Místo plného názvu modifikátoru můžete použít kratší název (alias): `
:::
+:::info Kompatibilita
+
+Požadavky bez odkazovače jsou porovnávány podle pravidel s `$~third-party` v AdGuardu pro Windows, AdGuardu pro Mac a AdGuardu pro Android s [CoreLibs][] v1.18 nebo novější.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` omezuje rozsah pravidla na požadavky **na** zadané domény a jejich subdomény. Chcete-li do jednoho pravidla přidat více domén, použijte jako oddělovací znak `|`.
@@ -821,7 +833,7 @@ Existuje sada modifikátorů, které lze použít k omezení oblasti použití p
:::info Kompatibilita
-V tom, jak AdGuard určuje typ obsahu na různých platformách, je velký rozdíl. U Rozšíření prohlížeče AdGuard je typ obsahu pro každý požadavek poskytován prohlížečem. AdGuard pro Windows, Mac a Android používají následující metodu: nejprve se aplikace pokusí určit typ požadavku podle záhlaví požadavku `Sec-Fetch-Dest` nebo podle přípony názvu souboru. Pokud není požadavek v této fázi zablokován, určí se typ pomocí záhlaví `Content-Type` na začátku odpovědi serveru.
+V tom, jak AdGuard určuje typ obsahu na různých platformách, existuje velký rozdíl. U Rozšíření prohlížeče AdGuard je typ obsahu pro každý požadavek poskytován prohlížečem. AdGuard pro Windows, Mac a Android používají následující metodu: nejprve se aplikace pokusí určit typ požadavku podle záhlaví požadavku `Sec-Fetch-Dest` nebo podle přípony názvu souboru. Pokud není požadavek v této fázi zablokován, určí se typ pomocí záhlaví `Content-Type` na začátku odpovědi serveru.
:::
@@ -1262,7 +1274,7 @@ Například tato pravidla jsou generická:
||domain.com^$domain=~example.com
```
-And these are not:
+A tato nejsou:
```adblock
domain.com###banner
@@ -1271,7 +1283,7 @@ domain.com###banner
#### **`$genericblock`** {#genericblock-modifier}
-Disables generic basic rules on pages that correspond to exception rule.
+Zakáže generická základní pravidla na stránkách, které odpovídají pravidlu výjimky.
**Příklady**
@@ -1281,19 +1293,19 @@ Disables generic basic rules on pages that correspond to exception rule.
:::caution Omezení
-In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything.
+V AdGuardu pro iOS a AdGuardu pro Safari fungují pravidla `$genericblock` jako [$document exclusion](#document-modifier) — odblokování všeho.
:::
:::info Kompatibilita
-Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3.
+Pravidla s modifikátorem `$genericblock` nejsou podporována Blokátorem obsahu AdGuard, AdGuardem pro Chrome MV3.
:::
#### **`$generichide`** {#generichide-modifier}
-Disables all generic [cosmetic rules](#cosmetic-rules) on pages that correspond to the exception rule.
+Zakáže všechna generická [kosmetická pravidla](#cosmetic-rules) na stránkách, které odpovídají pravidlu výjimky.
**Příklady**
@@ -1301,13 +1313,13 @@ Disables all generic [cosmetic rules](#cosmetic-rules) on pages that correspond
:::note
-You may use a shorter name (alias) instead of using the full modifier name: `$ghide`.
+Místo plného názvu modifikátoru můžete použít kratší název (alias): `$ghide`.
:::
#### **`specifichide`** {#specifichide-modifier}
-Disables all specific element hiding and CSS rules, but not general ones. Has an opposite effect to [`$generichide`](#generichide-modifier).
+Zakáže všechna specifická pravidla pro skrývání prvků a CSS, ale ne obecná pravidla. Má opačný účinek než [`$generichide`](#generichide-modifier).
**Příklady**
@@ -1315,25 +1327,25 @@ Disables all specific element hiding and CSS rules, but not general ones. Has an
:::note
-You may use a shorter name (alias) instead of using the full modifier name: `$shide`.
+Místo plného názvu modifikátoru můžete použít kratší název (alias): `$shide`.
:::
Zakazuje prohlížeči Google Chrome odesílat informace o verzi a modifikaci s požadavky na domény Google (včetně DoubleClick a Google Analytics).
-All cosmetic rules — not just specific ones — can be disabled by [`$elemhide` modifier](#elemhide-modifier).
+Všechna kosmetická pravidla — nejen ta specifická — lze zakázat pomocí modifikátoru [`$elemhide`](#elemhide-modifier).
:::
:::info Kompatibilita
-Rules with `$specifichide` modifier are not supported by AdGuard for iOS, AdGuard for Safari, and AdGuard Content Blocker.
+Pravidla s modifikátorem `$specifichide` nejsou AdGuardem pro iOS, Adguardem pro Safari a Blokátorem obsahu AdGuard podporována.
:::
### Pokročilé schopnosti {#advanced-modifiers}
-These modifiers are able to completely change the behavior of basic rules.
+Tyto modifikátory mohou zcela změnit chování základních pravidel.
@@ -1372,7 +1384,7 @@ These modifiers are able to completely change the behavior of basic rules.
#### **`$all`** {#all-modifier}
-`$all` modifier is made of [all content-types modifiers](#content-type-modifiers) and [`$popup`](#popup-modifier). E.g. rule `||example.org^$all` is converting into rule:
+`$all` modifikátor je složen ze [všech modifikátorů typů obsahu](#content-type-modifiers) a [`$popup`](#popup-modifier). Např. pravidlo `||example.org^$all` se převádí na pravidlo:
```adblock
||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup
@@ -1380,7 +1392,7 @@ These modifiers are able to completely change the behavior of basic rules.
:::caution Omezení
-This modifier cannot be used as an exception with the `@@` mark.
+Tento modifikátor nelze použít jako výjimku se znakem `@@`.
:::
@@ -1388,19 +1400,19 @@ This modifier cannot be used as an exception with the `@@` mark.
:::caution Omezení
-Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations).
+Vzhledem k tomu, že modifikátor `$popup` je součástí `$all`, modifikátor `$all` není podporován AdGuardem pro Chrome MV3 kcůli [`$popup` omezením modifikátoru](#popup-modifier-limitations).
:::
:::info Kompatibilita
-Rules with `$all` modifier are not supported by AdGuard Content Blocker.
+Pravidla s modifikátorem `$all` nejsou Blokátorem obsahu AdGuard podporována.
:::
#### **`$badfilter`** {#badfilter-modifier}
-The rules with the `$badfilter` modifier disable other basic rules to which they refer. It means that the text of the disabled rule should match the text of the `$badfilter` rule (without the `$badfilter` modifier).
+Pravidla s modifikátorem `$badfilter` vypnou ostatní základní pravidla, na která se vztahují. To znamená, že text vypnutého pravidla by měl odpovídat textu pravidla `$badfilter` (bez modifikátoru `$badfilter`).
**Příklady**
@@ -1409,12 +1421,12 @@ The rules with the `$badfilter` modifier disable other basic rules to which they
- `@@||example.com$badfilter` zakáže `@@||example.com`
- `||example.com$domain=domain.com,badfilter` zakáže `||example.com$domain=domain.com`
-Rules with `$badfilter` modifier can disable other basic rules for specific domains if they fulfill the following conditions:
+Pravidla s modifikátorem `$badfilter` mohou zakázat další základní pravidla pro konkrétní domény, pokud splňují následující podmínky:
-1. The rule has a `$domain` modifier
-1. The rule does not have a negated domain `~` in `$domain` modifier value
+1. Pravidlo má modifikátor `$domain`
+1. Pravidlo nemá hodnotu modifikátoru negované domény `~` v `$domain`
-In that case, the `$badfilter` rule will disable the corresponding rule for domains specified in both the `$badfilter` and basic rules. Please note that [wildcard-TLD logic](#wildcard-for-tld) works here as well.
+V takovém případě pravidlo `$badfilter` zakáže odpovídající pravidlo pro domény uvedené v pravidlech `$badfilter` i v základních pravidlech. Upozorňujeme, že [logika zástupných znaků TLD](#wildcard-for-tld) funguje i zde.
**Příklady**
@@ -1429,23 +1441,23 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma
:::caution Omezení
-In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples][badfilter-in-mv3].
+V [AdGuardu pro Chrome MV3][ext-mv3] se pravidlo s modifikátorem `$badfilter` použije v DNR pouze v případě, že úplně zruší zdrojové pravidlo. Nemůžeme ho vypočítat, pokud je zrušeno pouze částečně. [Příklady][badfilter-in-mv3].
:::
:::info Kompatibilita
-Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker.
+Pravidla s modifikátorem `$badfilter` nejsou Blokátorem obsahu AdGuard podporována.
:::
#### **`$cookie`** {#cookie-modifier}
-The `$cookie` modifier completely changes rule behavior. Instead of blocking a request, this modifier makes AdGuard suppress or modify the `Cookie` and `Set-Cookie` headers.
+Modifikátor `$cookie` zcela mění chování pravidla. Namísto blokování požadavku, tento modifikátor potlačí AdGuard nebo změní záhlaví `Cookie` a `Set-Cookie`.
-**Multiple rules matching a single request**
+**Vícenásobná pravidla odpovídajících jednomu požadavku**
-In case if multiple `$cookie` rules match a single request, we will apply each of them one by one.
+V případě, že jednomu požadavku odpovídá více pravidel `$cookie`, použijeme každé z nich.
**Syntaxe**
@@ -1459,20 +1471,20 @@ kde:
- **`seconds`** — počet sekund aktuálního času pro posunutí data vypršení platnosti souboru cookie.
- **`strategy`** — řetězec pro strategii [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite), která se má použít na cookies.
-For example,
+Např.
```adblock
||example.org^$cookie=NAME;maxAge=3600;sameSite=lax
```
-every time AdGuard encounters a cookie called `NAME` in a request to `example.org`, it will do the following:
+pokaždé, když AdGuard narazí na cookie s názvem `NAME` v požadavku na `example.org`, provede následující kroky:
- Nastaví datum vypršení platnosti na aktuální čas plus `3600` sekund
- Přiměje cookie použít "laxní" strategii [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite).
-**Escaping special characters**
+**Uvození speciálních znaků**
-If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`.
+Pokud je pro porovnání použit regulární výraz `name`, musí být dva znaky uvozeny: čárka `,` a znak dolaru `$`. Každý z nich označte zpětným lomítkem `\`. Např. uvozená čárka vypadá takto: `\,`.
**Příklady**
@@ -1481,7 +1493,7 @@ If regular expression `name` is used for matching, two characters must be escape
- `$cookie=/__utm[a-z]/` blokuje všude soubory cookie Google Analytics
- `||facebook.com^$third-party,cookie=c_user` brání Facebooku ve sledování, i když jste přihlášeni
-There are two methods to deactivate `$cookie` rules: the primary method involves using an exception marked with `@@` — `@@||example.org^$cookie`. The alternative method employs a `$urlblock` exception (also included under the `$document` exception alias — `$elemhide,jsinject,content,urlblock,extension`). Here's how it works:
+Existují dva způsoby, jak deaktivovat pravidla `$cookie`: primární metoda zahrnuje použití výjimky označené `@@` — `@@||example.org^$cookie`. Alternativní metoda využívá výjimku `$urlblock` (také zahrnutou pod aliasem výjimky `$document` — `$elemhide,jsinject,content,urlblock,extension`). Funguje to takto:
- `@@||example.org^$cookie` odblokuje všechny soubory cookie nastavené doménou `example.org`
- `@@||example.org^$urlblock` odblokuje všechny cookies nastavené doménou `example.org` a zakáže blokování všech požadavků odeslaných z `example.org`
@@ -1492,43 +1504,43 @@ There are two methods to deactivate `$cookie` rules: the primary method involves
:::caution Omezení
-In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules).
+V [AdGuardu pro Chrome MV3][ext-mv3] odstraňujeme soubory cookies dvěma způsoby: ze strany `content-script` (ke které máme přístup) a z `onBeforeSendHeaders` posluchače. Vzhledem k tomu, že `onBeforeSendHeaders` a další posluchači již nejsou blokováni, je nemůžeme ve všech případech smazat. Pomocí [tohoto testu](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules) můžete zkontrolovat, zda pravidlo funguje.
:::
:::caution Omezení
-`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`.
+Pravidla `$cookie` podporují tři typy modifikátorů: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party` a `strict-first-party`.
:::
:::info Kompatibilita
-Rules with `$cookie` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari.
+Pravidla s modifikátorem `$cookie` nejsou podporována Blokátorem obsahu AdGuard, AdGuardem pro iOS a AdGuardem pro Safari.
:::
#### **`$csp`** {#csp-modifier}
-This modifier completely changes the rule behavior. If it is applied to a rule, the rule will not block the matching request. Response headers will be modified instead.
+Tento modifikátor zcela mění chování pravidla. Pokud je použitý na pravidlo, pravidlo nezablokuje odpovídající požadavek. Namísto toho se upraví záhlaví odpovědí.
:::info
-In order to use this type of rules, it is required to have the basic understanding of the [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) security layer.
+Pro použití tohoto typu pravidel je nutné mít základní znalosti o vrstvě zabezpečení [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy).
:::
-For the requests matching a `$csp` rule, we will strengthen response security policy by enhancing the content security policy, similar to the content security policy of the `$csp` modifier contents. `$csp` rules are applied independently from any other rule type. **Only document-level exceptions** can influence it (see the examples section), but no other basic rules.
+U požadavků, které odpovídají pravidlu `$csp`, posílíme zásady zabezpečení odezvy posílením zásad zabezpečení obsahu, podobně jako u zásad zabezpečení obsahu modifikátoru obsahu `$csp`. Pravidla `$csp` jsou aplikována nezávisle na jakémkoli jiném typu pravidla. Mohou je ovlivnit **pouze výjimky na úrovni dokumentu** (viz část s příklady), ale žádná jiná základní pravidla.
-**Multiple rules matching a single request**
+**Vícenásobná pravidla odpovídajících jednomu požadavku**
-In case if multiple `$csp` rules match a single request, we will apply each of them.
+V případě, že jednomu požadavku odpovídá více pravidel `$csp`, použijeme každé z nich.
**Syntaxe**
-`$csp` value syntax is similar to the Content Security Policy header syntax.
+Syntaxe hodnoty `$csp` je podobná syntaxi záhlaví Content Security Policy.
-`$csp` value can be empty in the case of exception rules. See examples section below.
+Hodnota `$csp` může být v případě pravidel pro výjimky prázdná. Viz níže uvedený oddíl s příklady.
**Příklady**
@@ -1548,17 +1560,17 @@ In case if multiple `$csp` rules match a single request, we will apply each of t
:::info Kompatibilita
-Rules with `$csp` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari.
+Pravidla s modifikátorem `$csp` nejsou podporována Blokátorem obsahu AdGuard, AdGuardem pro iOS a AdGuardem pro Safari.
:::
#### **`$hls`** {#hls-modifier}
-`$hls` rules modify the response of a matching request. They are intended as a convenient way to remove segments from [HLS playlists (RFC 8216)](https://datatracker.ietf.org/doc/html/rfc8216).
+Pravidla `$hls` upravují odpověď na shodný požadavek. Jsou určena k pohodlnému odstraňování segmentů ze seznamů stop [HLS playlists (RFC 8216)](https://datatracker.ietf.org/doc/html/rfc8216).
:::note
-The word "segment" in this document means either a "Media Segment" or a "playlist" as part of a "Master Playlist": `$hls` rules do not distinguish between a "Master Playlist" and a "Media Playlist".
+Slovo "segment" v tomto dokumentu znamená buď "mediální segment" nebo "seznam skladeb" jako součást "hlavního seznamu skladeb": pravidla `$hls` nerozlišují mezi "hlavním seznamem skladeb" a "mediálním seznamem skladeb".
:::
@@ -1569,24 +1581,24 @@ The word "segment" in this document means either a "Media Segment" or a "playlis
- `t` — namísto testování adresy URL segmentu otestujte každý znak segmentu podle regulárního výrazu. Segment se shodným znakem je odstraněn;
- `i` — regulární výraz nerozlišuje velká a malá písmena.
-The characters `/`, `$` and `,` must be escaped with `\` inside `regexp`.
+Znaky `/`, `$` a `,` musí být uvnitř `regexp` uvozeny pomocí `\`.
**Výjimky**
-Basic URL exceptions shall not disable rules with the `$hls` modifier. They can be disabled as described below:
+Základní výjimky URL nesmí zakázat pravidla s modifikátorem `$hls`. Lze je zakázat, jak je popsáno níže:
- `@@||example.org^$hls` zakáže všechna pravidla `$hls` pro odpovědi z URL odpovídajících `||example.org^`.
- `@@||example.org^$hls=text` zakáže všechna pravidla `$hls` s hodnotou modifikátoru `$hls` shodným s `text` pro odpovědi z URL odpovídajících `||example.org^`.
:::tip
-`$hls` rules can also be disabled by `$document`, `$content` and `$urlblock` exception rules.
+Pravidla `$hls` lze také zakázat pravidly výjimek `$document`, `$content` a `$urlblock`.
:::
:::note
-When multiple `$hls` rules match the same request, their effect is cumulative.
+Když vícenásobná pravidla `$hls` odpovídají stejnému požadavku, jejich účinek je kumulativní.
:::
@@ -1596,26 +1608,26 @@ When multiple `$hls` rules match the same request, their effect is cumulative.
- `||example.org^$hls=/\/videoplayback\/?\?.*\&source=dclk_video_ads/i` dosáhne víceméně téhož pomocí regulárního výrazu namísto vzoru URL.
- `||example.org^$hls=/#UPLYNK-SEGMENT:.*\,ad/t` odstraní všechny segmenty, které mají odpovídající znak.
-**Anatomy of an HLS playlist**
+**Anatomie seznamu stop HLS**
-A quick summary of the [specification](https://datatracker.ietf.org/doc/html/rfc8216):
+Stručné shrnutí [specifikace](https://datatracker.ietf.org/doc/html/rfc8216):
-1. An HLS playlist is a collection of text lines
-1. A line may be empty, a comment (starts with `#`), a tag (also starts with `#`, can only be recognized by name) or a URL
-1. A URL line is called a "segment"
-1. Tags may apply to a single segment, i.e. the first URL line after the tag, to all segments following the tag and until the tag with the same name, or to the whole playlist
+1. Seznam stop HLS je kolekce textových řádků
+1. Řádek může být prázdný, komentář (začíná `#`), znak (také začíná `#`, lze jej rozpoznat pouze podle názvu) nebo URL
+1. Řádek URL se nazývá "segment"
+1. Znaky se mohou vztahovat na jeden segment, tj. první řádek adresy URL za znakem, na všechny segmenty následující za znakem až do znaku se stejným názvem nebo na celý seznam skladeb
-Some points specific to the operation of `$hls` rules:
+Některé specifické body týkající se fungování pravidel `$hls`:
-1. When a segment is removed, all of the tags that apply only to that segment are also removed
-1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed
-1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules
-1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist
+1. Při odstranění segmentu se odstraní také všechny znaky, které se vztahují pouze k tomuto segmentu
+1. Pokud se znak vztahuje na více segmentů a všechny tyto segmenty jsou odstraněny, je odstraněna i znak
+1. Protože neexistuje způsob, jak rozpoznat různé druhy znaků podle syntaxe, rozpoznáváme všechny znaky uvedené v RFC a některé nestandardní znaky, se kterými jsme se setkali v praxi. Všechny řádky začínající na `#`. Ty, které nejsou rozpoznány jako znak, jsou předány bez úprav a nejsou porovnávány s pravidly
+1. Značky nebudou přiřazeny, pokud se vztahují na celý seznam stop a k jejich odstranění nelze použít pravidla `$hls`, protože tyto typy pravidel jsou určeny pro odstraňování segmentů. Pokud víte, co děláte, můžete pomocí pravidel `$replace` odstranit nebo přepsat pouze jeden znak ze seznamu skladeb
-**An example of a transformation done by the rules:**
+**Příklad transformace provedené podle pravidel:**
-Original response
+Původní odezva
```text
#EXTM3U
@@ -1642,7 +1654,7 @@ preroll.ts
-Applied rules
+Použitá pravidla
```adblock
||example.org^$hls=preroll
@@ -1652,7 +1664,7 @@ preroll.ts
-Modified response
+Modifikovaná odpověď
```text
#EXTM3U
@@ -1680,13 +1692,13 @@ preroll.ts
:::info Kompatibilita
-Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.10 or later.
+Pravidla s modifikátorem `$hls` jsou podporována AdGuardem pro Windows, Mac a Android s [CoreLibs][] v1.10 nebo novější.
:::
#### **`$inline-script`** {#inline-script-modifier}
-The `$inline-script` modifier is designed to block inline JavaScript embedded into the web page, using Content Security Policy (CSP). It improves security and privacy by preventing application of inline ads or potentially malicious scripts. The rule `||example.org^$inline-script` is converting into the CSP-syntax rule:
+Modifikátor `$inline-script` je určen k blokování in-line JavaScriptu vloženého do webové stránky pomocí zásad zabezpečení obsahu (CSP). Zlepšuje zabezpečení a soukromí tím, že zabraňuje použití in-line reklam nebo potenciálně škodlivých skriptů. Pravidlo `||example.org^$inline-script` se převádí na syntaxi pravidel CSP:
```adblock
||example.org^$csp=script-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem:
@@ -1694,7 +1706,7 @@ The `$inline-script` modifier is designed to block inline JavaScript embedded in
#### **`$inline-font`** {#inline-font-modifier}
-The `$inline-font` modifier is designed to block inline fonts embedded into the web page, using Content Security Policy (CSP). It improves security and privacy by preventing application of inline fonts that could be used for data collection and fingerprinting. The rule `||example.org^$inline-font` is converting into the CSP-syntax rule:
+Modifikátor `$inline-font` je určen k blokování in-line fontů vložených do webové stránky pomocí zásad zabezpečení obsahu (CSP). Zlepšuje zabezpečení a soukromí tím, že zabraňuje použití in-line fontů, které by mohly být použity ke shromažďování dat a čtení digitálních otisků. Pravidlo `||example.org^$inline-font` se převádí na syntaxi pravidel CSP:
```adblock
||example.org^$csp=font-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem:
@@ -1702,46 +1714,46 @@ The `$inline-font` modifier is designed to block inline fonts embedded into the
#### **`$jsonprune`** {#jsonprune-modifier}
-`$jsonprune` rules modify the response to a matching request by removing JSON items that match a modified [JSONPath](https://goessner.net/articles/JsonPath/) expression. They do not modify responses which are not valid JSON documents.
+Pravidla `$jsonprune` upravují odpověď na odpovídající požadavek odstraněním položek JSON, které odpovídají upravenému výrazu [JSONPath](https://goessner.net/articles/JsonPath/). Nemění odpovědi, které nejsou platnými dokumenty JSON.
-In AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, `$jsonprune` also supports modifying JSONP (padded JSON) documents.
+V AdGuardu pro Windows, Mac a Android s [CoreLibs][] v1.11 nebo novější, `$jsonprune` podporuje také úpravu dokumentů JSONP (padded JSON).
**Syntaxe**
- `||example.org^$jsonprune=expression` odstraní z odpovědi položky, které odpovídají upravenému výrazu JSONPath `expression`.
-Due to the way rule parsing works, the characters `$` and `,` must be escaped with `\` inside `expression`.
+Vzhledem ke způsobu zpracování pravidel musí být znaky `$` a `,` uvnitř `výrazu` uvozeny pomocí `\`.
-The modified JSONPath syntax has the following differences from the original:
+Upravená syntaxe JSONPath má oproti původní následující rozdíly:
-1. Script expressions are not supported
-1. The supported filter expressions are:
- - `?(has )` — true if the current object has the specified key
- - `?(key-eq )` — true if the current object has the specified key, and its value is equal to the specified value
- - `?(key-substr )` — true if the specified value is a substring of the value of the specified key of the current object
-1. Whitespace outside of double- or single-quoted strings has no meaning
-1. Both double- and single-quoted strings can be used
-1. Expressions ending with `..` are not supported
-1. Multiple array slices can be specified in square brackets
+1. Výrazy skriptů nejsou podporovány
+1. Podporované výrazy filtrů jsou:
+ - `?(has )` — "true", pokud má aktuální objekt zadaný klíč
+ - `?(key-eq )` — "true", pokud má aktuální objekt zadaný klíč a jeho hodnota se rovná zadané hodnotě
+ - `?(key-substr )` — "true", pokud je zadaná hodnota podřetězcem hodnoty zadaného klíče aktuálního objektu
+1. Mezery mimo řetězce s dvojitými nebo jednoduchými uvozovkami nemají žádný význam
+1. Lze použít řetězce s dvojitými i jednoduchými uvozovkami
+1. Výrazy končící na `..` nejsou podporovány
+1. V hranatých závorkách lze zadat vícero dílků pole
-There are various online tools that make working with JSONPath expressions more convenient:
+Existují různé online nástroje, které usnadňují práci s výrazy JSONPath:
https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfinder.com/ https://jsonpath.com/
-Keep in mind, though, that all JSONPath implementations have unique features/quirks and are subtly incompatible with each other.
+Mějte však na paměti, že všechny implementace JSONPath mají jedinečné vlastnosti a jsou vzájemně nekompatibilní.
**Výjimky**
-Basic URL exceptions shall not disable rules with the `$jsonprune` modifier. They can be disabled as described below:
+Základní výjimky URL nesmí zakázat pravidla s modifikátorem `$jsonprune`. Lze je zakázat, jak je popsáno níže:
- `@@||example.org^$jsonprune` zakáže všechna pravidla `$jsonprune` pro odpovědi z URL odpovídajících `||example.org^`.
- `@@||example.org^$jsonprune=text` zakáže všechna pravidla `$jsonprune` s hodnotou modifikátoru `$jsonprune` shodným s `text` pro odpovědi z URL odpovídajících `||example.org^`.
-`$jsonprune` rules can also be disabled by `$document`, `$content` and `$urlblock` exception rules.
+Pravidla `$jsonprune` lze také zakázat pravidly výjimek `$document`, `$content` a `$urlblock`.
:::note
-When multiple `$jsonprune` rules match the same request, they are sorted in lexicographical order, the first rule is applied to the original response, and each of the remaining rules is applied to the result of applying the previous one.
+Když vícenásobná pravidla `$jsonprune` odpovídají stejnému požadavku, jsou seřazena v lexikografickém pořadí, první pravidlo je aplikováno na původní odpověď a každé ze zbývajících pravidel je aplikováno na výsledek použití předchozího.
:::
@@ -1750,7 +1762,7 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
- `||example.org^$jsonprune=\$..[one\, "two three"]` odstraní všechny výskyty klíčů "one" a "two three" kdekoli v dokumentu JSON.
-Input
+Vstup
```json
{
@@ -1765,7 +1777,7 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
-Output
+Výstup
```json
{
@@ -1780,7 +1792,7 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
- `||example.org^$jsonprune=\$.a[?(has ad_origin)]` odstraní všechny potomky `a`, které mají klíč `ad_origin`.
-Input
+Vstup
```json
{
@@ -1799,7 +1811,7 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
-Output
+Výstup
```json
{
@@ -1816,7 +1828,7 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
- `||example.org^$jsonprune=\$.*.*[?(key-eq 'Some key' 'Some value')]` odstraní všechny položky, které jsou na úrovni vnoření 3 a mají vlastnost "Some key" rovnu "Some value".
-Input
+Vstup
```json
{
@@ -1828,7 +1840,7 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
-Output
+Výstup
```json
{
@@ -1839,14 +1851,14 @@ When multiple `$jsonprune` rules match the same request, they are sorted in lexi
-**Nested JSONPath expressions**
+**Vnořené výrazy JSONPath**
-In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPath expressions may be used as keys in filter expressions.
+V AdGuardu pro Windows, Mac a Android s [CoreLibs][] v1.11 nebo novější, lze výrazy JSONPath použít jako klíče ve výrazech filtru.
- `||example.org^$jsonprune=\$.elems[?(má "\$.abc")]` odstraní všechny potomky `elems`, které mají vlastnost volitelnou výrazem JSONPath `$.abc`.
-Input
+Vstup
```json
{
@@ -1866,7 +1878,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa
-Output
+Výstup
```json
{
@@ -1884,7 +1896,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa
- `||example.org^$jsonprune=\$.elems[?(key-eq "\$.a.b.c" "abc")]` odstraní všechny potomky `elems`, které mají vlastnost volitelnou pomocí výrazu JSONPath `$.a.b.c` s hodnotou rovnou `"abc"`.
-Input
+Vstup
```json
{
@@ -1902,7 +1914,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa
-Output
+Výstup
```json
{
@@ -1925,32 +1937,32 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa
:::info Kompatibilita
-Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.10 or later.
+Pravidla s modifikátorem `$jsonprune` jsou podporována AdGuardem pro Windows, Mac, Android a Linux s [CoreLibs][] v1.10 nebo novější.
:::
#### **`$xmlprune`** {#xmlprune-modifier}
-`$xmlprune` rules modify the response to a matching request by removing XML items that match an [XPath 1.0](https://www.w3.org/TR/1999/REC-xpath-19991116/) expression. The expression must return a [node-set](https://www.w3.org/TR/1999/REC-xpath-19991116/#node-sets). `$xmlprune` rules do not modify responses which are not well-formed XML documents.
+Pravidla `$xmlprune` upravují odpověď na odpovídající požadavek odstraněním položek XML, které odpovídají upravenému výrazu[XPath 1.0](https://www.w3.org/TR/1999/REC-xpath-19991116/). Výraz musí vrátit [node-set](https://www.w3.org/TR/1999/REC-xpath-19991116/#node-sets). `$xmlprune` pravidla neupravují odpovědi, které nejsou dobře formulovanými dokumenty XML.
**Syntaxe**
- `||example.org^$xmlprune=expression` odstraní z odpovědi položky, které odpovídají výrazu XPath `expression`.
-Due to the way rule parsing works, the characters `$` and `,` must be escaped with `\` inside `expression`.
+Vzhledem ke způsobu zpracování pravidel musí být znaky `$` a `,` uvnitř `výrazu` uvozeny pomocí `\`.
**Výjimky**
-Basic URL exceptions shall not disable rules with the `$xmlprune` modifier. They can be disabled as described below:
+Základní výjimky URL nesmí zakázat pravidla s modifikátorem `$xmlprune`. Lze je zakázat, jak je popsáno níže:
- `@@||example.org^$xmlprune` zakáže všechna pravidla `$xmlprune` pro odpovědi z URL odpovídajících `||example.org^`.
- `@@||example.org^$xmlprune=text` zakáže všechna pravidla `$xmlprune` s hodnotou modifikátoru `$xmlprune` shodným s `text` pro odpovědi z URL odpovídajících `||example.org^`.
-`$xmlprune` rules can also be disabled by `$document`, `$content` and `$urlblock` exception rules.
+Pravidla `$xmlprune` lze také zakázat pravidly výjimek `$document`, `$content` a `$urlblock`.
:::note
-When multiple `$xmlprune` rules match the same request, they are applied in lexicographical order.
+Když je více pravidel `$xmlprune` odpovídá stejnému požadavku, jsou použita v lexikografickém pořadí.
:::
@@ -1959,7 +1971,7 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
- `||example.org^$xmlprune=/bookstore/book[position() mod 2 = 1]` odstraní z knihkupectví knihy s lichými čísly.
-Input
+Vstup
```xml
@@ -2004,7 +2016,7 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
-Output
+Výstup
```xml
@@ -2037,7 +2049,7 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
- `||example.org^$xmlprune=/bookstore/book[year = 2003]` odstraní knihy z roku 2003 z knihkupectví.
-Input
+Vstup
```xml
@@ -2082,7 +2094,7 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
-Output
+Výstup
```xml
@@ -2115,7 +2127,7 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
- `||example.org^$xmlprune=//*/@*` odstraní všechny atributy ze všech prvků.
-Input
+Vstup
```xml
@@ -2135,7 +2147,7 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
-Output
+Výstup
```xml
@@ -2163,24 +2175,24 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi
:::info Kompatibilita
-Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.15 or later.
+Pravidla s modifikátorem `$xmlprune` jsou podporována AdGuardem pro Windows, Mac, Android a Linux s [CoreLibs][] v1.15 nebo novější.
:::
#### **`$network`** {#network-modifier}
-This is basically a Firewall-like rule allowing to fully block or unblock access to a specified remote address.
+Jedná se v podstatě o pravidla typu brány Firewall, která umožňují plně zablokovat nebo odblokovat přístup na zadanou vzdálenou adresu.
-1. `$network` rules match **IP addresses only**! You cannot use them to block or unblock access to a domain.
-2. To match an IPv6 address, you have to use the collapsed syntax, e.g. use `[2001:4860:4860::8888]$network` instead of `[2001:4860:4860:0:0:0:0:8888]$network`.
-3. An allowlist `$network` rule makes AdGuard bypass data to the matching endpoint, hence there will be no further filtering at all.
-4. If the IP part starts and ends with `/` character, it is treated as a regular expression.
+1. Pravidla `$network` odpovídají **pouze IP adresám**! Nelze je použít k zablokování nebo odblokování přístupu k doméně.
+2. Chcete-li se shodovat s adresou IPv6, musíte použít sbalenou syntaxi, např. `[2001:4860:4860::8888]$network` namísto `[2001:4860:4860:0:0:0:0:8888]$network`.
+3. Pravidlo seznamu povolených `$network` způsobí, že AdGuard bude obcházet data odpovídajícího koncového bodu, proto nebude provádět žádné další filtrování.
+4. Pokud část IP začíná a končí znakem `/`, je považována za regulární výraz.
-We recommend to get acquainted with this [article](#regexp-support) for better understanding of regular expressions.
+Pro lepší pochopení regulárních výrazů doporučujeme seznámit se s tímto [článkem](#regexp-support).
:::caution Omezení
-The `$network` modifier can only be used in rules together with the `$app` and `$important` modifiers, and not with any other modifiers.
+Modifikátor `$network` lze v pravidlech použít pouze společně s modifikátory `$app` a `$important`, nikoli s žádnými jinými modifikátory.
:::
@@ -2195,32 +2207,32 @@ The `$network` modifier can only be used in rules together with the `$app` and `
:::info Kompatibilita
-Only AdGuard for Windows, Mac, and Android are technically capable of using rules with `$network` modifier.
+Pouze AdGuard pro Windows, Mac a Android jsou technicky schopné používat pravidla s modifikátorem `$network`.
:::
#### **`$permissions`** {#permissions-modifier}
-This modifier completely changes the rule behavior. If it is applied to a rule, the rule will not block the matching request. Response headers will be modified instead.
+Tento modifikátor zcela mění chování pravidla. Pokud je použitý na pravidlo, pravidlo nezablokuje odpovídající požadavek. Namísto toho se upraví záhlaví odpovědí.
:::info
-In order to use this type of rules, it is required to have a basic understanding of the [Permissions Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Permissions_Policy) security layer.
+Pro použití tohoto typu pravidel je nutné mít základní znalosti o vrstvě zabezpečení [Permissions Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Permissions_Policy).
:::
-For the requests matching a `$permissions` rule, AdGuard strengthens response's permissions policy by adding an additional permission policy equal to the `$permissions` modifier contents. `$permissions` rules are applied independently from any other rule type. **Only document-level exceptions** can influence it (see the examples section), but no other basic rules.
+U požadavků, které odpovídají pravidlu `$permissions`, AdGuard posiluje zásady funkcí odpovědi přidáním dalších zásad oprávnění, které se rovnají obsahu modifikátoru `$permissions`. Pravidla `$permissions` jsou aplikována nezávisle na jakémkoli jiném typu pravidla. Mohou je ovlivnit **pouze výjimky na úrovni dokumentu** (viz část s příklady), ale žádná jiná základní pravidla.
**Syntaxe**
-`$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions:
+Hodnota syntaxe `$permissions` je shodná se [syntaxí](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) záhlaví `Permissions-Policy` s následujícími výjimkami:
-1. A comma that separates multiple features **MUST** be escaped — see examples below.
-2. A pipe character (`|`) can be used instead of a comma to separate features.
+1. Čárka, která odděluje více prvků **MUSÍ být uvozena** – viz příklady níže.
+2. Místo čárky lze pro oddělení funkcí použít znak `(|)`.
-The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives).
+Seznam dostupných direktiv je k dispozici [zde](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives).
-`$permissions` value can be empty in the case of exception rules — see examples below.
+Hodnota `$permissions` může být v případě pravidel pro výjimky prázdná — viz příklady níže.
**Příklady**
@@ -2233,13 +2245,13 @@ The list of available directives is available [here](https://developer.mozilla.o
:::note
-`$permissions` rules only take effect for main frame and sub frame requests. This means they are applied when a page is loaded or when an iframe is loaded.
+Pravidla `$permissions` jsou účinná pouze pro požadavky hlavního rámce a vedlejšího rámce. To znamená, že se použijí při načtení stránky nebo iframe.
:::
:::note
-If there are multiple `$permissions` rules that match the same request, multiple `Permissions-Policy` headers will be added to the response for each rule with their `$permissions` value. So if you have two rules: `||example.org^$permissions=autoplay=()` and `||example.org^$permissions=geolocation=()\,camera=()` that match the same request, the response will contain two `Permissions-Policy` headers: `autoplay=()` and `geolocation=()\,camera=()`.
+Pokud existuje více pravidel `$permissions`, která odpovídají stejnému požadavku, bude do odpovědi přidáno více záhlaví `Permissions-Policy` pro každé pravidlo s jejich hodnotou `$permissions`. Pokud tedy máte dvě pravidla: `||example.org^$permissions=autoplay=()` a `||example.org^$permissions=geolocation=()\,camera=()`, která odpovídají stejnému požadavku, bude odpověď obsahovat dvě záhlaví `Permissions-Policy`: `autoplay=()` a `geolocation=()\,camera=()`.
:::
@@ -2247,15 +2259,15 @@ If there are multiple `$permissions` rules that match the same request, multiple
:::caution Omezení
-Firefox ignores the `Permissions-Policy` header. For more information, see [this issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1694922).
+Firefox ignoruje záhlaví `Permissions-Policy`. Další informace naleznete v [tomto hlášení](https://bugzilla.mozilla.org/show_bug.cgi?id=1694922).
:::
:::caution Omezení
-1. Characters forbidden in the `$permissions` value: `$`.
-2. `$permissions` is compatible with a limited set of modifiers: `$domain`, `$important`, `$subdocument`, and [content-type modifiers](#content-type-modifiers).
-3. `$permissions` rules that do not have any [content-type modifiers](#content-type-modifiers) will match only requests where content type is `document`.
+1. Zakázané znaky v `$permissions` hodnotě: `$`.
+2. `$permissions` je kompatibilní s omezenou sadou modifikátorů: `$domain`, `$important`, `$subdocument` a [modifikátory typu obsahu](#content-type-modifiers).
+3. Pravidla `$permissions`, která neobsahují žádné modifikátory typu obsahu [](#content-type-modifiers), budou odpovídat pouze požadavkům, jejichž typem obsahu je `document`.
:::
@@ -2268,15 +2280,15 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this
#### **`$redirect`** {#redirect-modifier}
-AdGuard is able to redirect web requests to a local "resource".
+AdGuard je schopen přesměrovat webové požadavky na místní "zdroj".
**Syntaxe**
-AdGuard uses the same filtering rule syntax as uBlock Origin. Also, it is compatible with ABP `$rewrite=abp-resource` modifier.
+AdGuard používá stejnou syntaxi pravidel filtrování jako uBlock Origin. Je také kompatibilní s modifikátorem ABP `$rewrite=abp-resource`.
-`$redirect` is a modifier for the [basic filtering rules](#basic-rules) so rules with this modifier support all other basic modifiers like `$domain`, `$third-party`, `$script`, etc.
+`$redirect` je modifikátor pro [základní pravidla filtrování](#basic-rules), takže pravidla s tímto modifikátorem podporují všechny ostatní základní modifikátory, jako jsou `$domain`, `$third-party`, `$script` atd.
-The value of the `$redirect` modifier must be the name of the resource that will be used for redirection.
+Hodnota modifikátoru `$redirect` musí být název zdroje, který bude použit pro přesměrování.
##### Zakázání pravidel `$redirect`
@@ -2285,15 +2297,15 @@ The value of the `$redirect` modifier must be the name of the resource that will
- `@@||example.org^$redirect` zakáže všechna pravidla `$redirect` pro URL adresy, které odpovídají `||example.org^`.
- `@@||example.org^$redirect=nooptext` zakáže všechna pravidla s `$redirect=nooptext` pro všechny požadavky, které odpovídají `||example.org^`.
-More information on redirects and their usage is available [on GitHub](https://github.com/AdguardTeam/Scriptlets#redirect-resources).
+Další informace o přesměrování a použití jsou k dispozici [na GitHubu](https://github.com/AdguardTeam/Scriptlets#redirect-resources).
##### Priority pravidel `$redirect` {#redirect-rule-priorities}
-`$redirect` rules have higher priority than regular basic blocking rules. This means that if there is a basic blocking rule, the `$redirect` rule will override it. Allowlist rules with `@@` mark have higher priority than `$redirect` rules. If a basic rule with the `$important` modifier and the `$redirect` rule matches the same URL, the latter is overridden unless it's also marked as `$important`.
+Pravidla `$redirect` mají vyšší prioritu než běžná základní pravidla blokování. To znamená, že pokud existuje základní pravidlo blokování, pravidlo `$redirect` jej přepíše. Pravidla seznamu povolených se znakem `@@` mají vyšší prioritu než pravidla `$redirect`. Pokud se základní pravidlo s modifikátorem `$important` a pravidlem `$redirect` shoduje se stejnou adresou URL, je druhé pravidlo přepsáno, pokud není též označeno jako `$important`.
-**In short: `$important` > `@@` > `$redirect` > `basic rules`.**
+**Ve zkratce: `$important` > `@@` > `$redirect` > `basic rules`.**
Další podrobnosti najdete v [prioritách pravidel](#rule-priorities).
@@ -2301,7 +2313,7 @@ Další podrobnosti najdete v [prioritách pravidel](#rule-priorities).
:::caution Omezení
-In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported.
+V [AdGuardu pro Chrome MV3][ext-mv3] nejsou podporována pravidla `$redirect`.
:::
@@ -2314,11 +2326,11 @@ In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not su
#### **`$redirect-rule`** {#redirect-rule-modifier}
-This is basically an alias to [`$redirect`](#redirect-modifier) since it has the same "redirection" values and the logic is almost similar. The difference is that `$redirect-rule` is applied only in the case when the target request is blocked by a different basic rule.
+Toto je v podstatě alias [`$redirect`](#redirect-modifier), protože má stejné hodnoty "přesměrování" a logika je téměř podobná. Rozdíl je v tom, že `$redirect-rule` se použije pouze v případě, kdy je cílový požadavek blokován jiným základním pravidlem.
Další podrobnosti najdete v [prioritách pravidel](#rule-priorities).
-Negating `$redirect-rule` works exactly the same way as for regular `$redirect` rules. Even more than that, `@@||example.org^$redirect` will negate both `$redirect` and `$redirect-rule` rules.
+Negace `$redirect-rule` funguje úplně stejně jako u běžných pravidel `$redirect`. Ještě více než to, bude `@@||example.org^$redirect` negovat jak pravidla `$redirect`, tak `$redirect-rule`.
**Příklady**
@@ -2327,21 +2339,21 @@ Negating `$redirect-rule` works exactly the same way as for regular `$redirect`
||example.org^$redirect-rule=noopjs
```
-In this case, only requests to `example.org/script.js` will be "redirected" to `noopjs`. All other requests to `example.org` will be kept intact.
+V tomto případě budou pouze požadavky na `example.org/script.js` "přesměrovány" na `noopjs`. Všechny ostatní požadavky na `example.org` zůstanou nedotčeny.
:::info Kompatibilita
-Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open.
+Pravidla s modifikátorem `$redirect-rule` nejsou podporována [Blokátorem obsahu AdGuard][and-cb], [AdGuardem pro iOS][ios-app], [AdGuardem pro Safari][ext-saf] a [AdGuardem pro Chrome MV3][ext-mv3]. [Diskuse o přidání podpory pro pravidla `$redirect-rule` v rozšířeních Chrome MV3](https://github.com/w3c/webextensions/issues/493) je aktuálně otevřená.
:::
#### **`$referrerpolicy`** {#referrerpolicy-modifier}
-These rules allow overriding of a page's [referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy). Responses to matching requests will have all of their `Referrer-Policy` headers replaced with a single header with the value equal to the matching rule's modifier value. If the response carries an HTML document with a `)[\s\S]*<\/VAST>/\$1<\/VAST>/i
```
-There are three parts in this rule:
+Toto pravidlo má tři části:
- `regexp` — `()(.|\s)*<\/VAST>`;
- `replacement` — `\$1<\/VAST>` kde `$` je uvozeno;
- `modifiers` — `i` pro necitlivé vyhledávání.
-You can see how this rule works here: http://regexr.com/3cesk
+Jak toto pravidlo funguje, se můžete podívat zde: http://regexr.com/3cesk
-**Multiple `$replace` rules**
+**Vícenásobná pravidla `$replace`**
1. `||example.org^$replace=/X/Y/`
2. `||example.org^$replace=/Z/Y/`
@@ -2787,7 +2799,7 @@ You can see how this rule works here: http://regexr.com/3cesk
- Jak pravidlo 1, tak pravidlo 2 se použijí na všechny požadavky odeslané na `example.org`.
- Pravidlo 2 je zakázáno pro požadavky odpovídající na `||example.org/page/`, **ale pravidlo 1 stále funguje!**
-**Disabling `$replace` rules**
+**Zakázání pravidel `$replace`**
- `@@||example.org^$replace` zakáže všechna pravidla `$replace` odpovídající na `||example.org^`.
- `@@||example.org^$document` nebo `@@||example.org^$content` zakáže všechna pravidla `$replace` **pocházející ze** stránek `example.org` **včetně stránky samotné**.
@@ -2801,29 +2813,29 @@ You can see how this rule works here: http://regexr.com/3cesk
:::info Kompatibilita
-Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level.
+Pravidla s modifikátorem `$replace` podporuje AdGuard pro Windows, Mac, Android a Rozšíření prohlížeče AdGuard pro Chrome, Firefox a Edge. Taková pravidla v rozšířeních pro jiné prohlížeče nefungují, protože nemohou měnit obsah na úrovni sítě.
:::
#### **`$urltransform`** {#urltransform-modifier}
-The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression.
+Pravidla `$urltransform` vám umožňují upravit URL požadavku nahrazením textu, který odpovídá regulárnímu výrazu.
-**Features**
+**Funkce**
- Pravidla `$urltransform` se obvykle vztahují pouze na části URL týkající se cesty a dotazu, viz níže jedna výjimka.
- `$urltransform` nebude použito, pokud je původní URL blokována jinými pravidly.
- `$urltransform` se použije před pravidly `$removeparam`.
-The `$urltransform` value can be empty for exception rules.
+Hodnota `$urltransform` může být pro pravidla výjimek prázdná.
-**Multiple rules matching a single request**
+**Vícenásobná pravidla odpovídajících jednomu požadavku**
-If multiple `$urltransform` rules match a single request, we will apply each of them. **The order is defined alphabetically.**
+Pokud jednomu požadavku odpovídá více pravidel `$urltransform`, použijeme každé z nich. **Pořadí je stanoveno abecedně.**
**Syntaxe**
-`$urltransform` syntax is similar to replacement with regular expressions [in Perl](http://perldoc.perl.org/perlrequick.html#Search-and-replace).
+`$urltransform` syntaxe je podobná nahrazování regulárními výrazy [v Perl](http://perldoc.perl.org/perlrequick.html#Search-and-replace).
```text
urltransform = "/" regexp "/" replacement "/" modifiers
@@ -2833,17 +2845,17 @@ urltransform = "/" regexp "/" replacement "/" modifiers
- **`replacement`** — řetězec, který bude použit k nahrazení řetězce odpovídajícího `regexp`.
- **`modifiers`** — příznaky regulárního výrazu. Například `i` — necitlivé vyhledávání nebo `s` — jednořádkový režim.
-In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`.
+V hodnotě `$urltransform` musí být dva znaky uvozeny: čárka `,` a znak dolaru `$`. K tomu použijte znak zpětného lomítka `\`. Např. uvozená čárka vypadá takto: `\,`.
-**Changing the origin**
+**Změna původu**
:::info Kompatibilita
-This section only applies to AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.17 or later.
+Tato část platí pouze pro AdGuard pro Windows, AdGuard pro Mac, AdGuard pro Android a Adguardem pro Linux s [CoreLibs][] v1.17 nebo novější.
:::
-As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`).
+Jak bylo uvedeno výše, pravidla `$urltransform` mohou normálně měnit pouze část URL obsahující cestu a dotaz. Pokud však pravidlo `regexp` začíná řetězcem `^http`, pak se prohledává celá adresa URL a pravidlo ji může upravit. Takové pravidlo se neuplatní, pokud transformace adresy URL nelze dosáhnout přesměrováním HTTP (například pokud je metoda požadavku `POST`).
**Příklady**
@@ -2851,13 +2863,13 @@ As stated above, normally `$urltransform` rules are only allowed to change the p
||example.org^$urltransform=/(pref\/).*\/(suf)/\$1\$2/i
```
-There are three parts in this rule:
+Toto pravidlo má tři části:
- `regexp` — `(pref\/).*\/(suf)`;
- `replacement` — `\$1\$2` kde `$` je uvozeno;
- `modifiers` — `i` pro necitlivé vyhledávání.
-**Multiple `$urltransform` rules**
+**Vícenásobná pravidla `$urltransform`**
1. `||example.org^$urltransform=/X/Y/`
2. `||example.org^$urltransform=/Z/Y/`
@@ -2866,63 +2878,63 @@ There are three parts in this rule:
- Jak pravidlo 1, tak pravidlo 2 se použijí na všechny požadavky odeslané na `example.org`.
- Pravidlo 2 je zakázáno pro požadavky odpovídající na `||example.org/page/`, **ale pravidlo 1 stále funguje!**
-**Re-matching rules after transforming the URL**
+**Opětovná shoda pravidel po transformaci URL**
-After applying all matching `$urltransform` rules, the transformed request will be matched against all other rules:
+Po použití všech odpovídajících pravidel `$urltransform` bude transformovaný požadavek porovnán se všemi ostatními pravidly:
-E.g., with the following rules:
+Např. s následujícími pravidly:
```adblock
||example.com^$urltransform=/firstpath/secondpath/
||example.com/secondpath^
```
-the request to `https://example.com/firstpath` will be blocked.
+požadavek na `https://example.com/firstpath` bude zablokován.
-**Disabling `$urltransform` rules**
+**Zakázání pravidel `$urltransform`**
- `@@||example.org^$urltransform` zakáže všechna pravidla `$urltransform` odpovídající na `||example.org^`.
- `@@||example.org^$urltransform=/Z/Y/` zakáže pravidlo s `$urltransform=/Z/Y/` pro jakýkoliv požadavek, který odpovídá `||example.org^`.
-`$urltransform` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$urltransform=/X/Y/` for requests to **example.com**, but `@@||example.com^$urlblock` will.
+Pravidla `$urltransform` lze také zakázat pravidly výjimek `$document` a `$urlblock`. Základní pravidla pro výjimky bez modifikátorů to však nedělají. Např. `@@||example.com^` nezakáže `$urltransform=/X/Y/` pro požadavky na **example.com**, ale `@@||example.com^$urlblock` ano.
-**The rule example for cleaning affiliate links**
+**Příklad pravidla pro čištění partnerských odkazů**
-Many websites use tracking URLs to monitor clicks before redirecting to the actual destination. These URLs contain marketing parameters and analytics tokens that can be removed to improve privacy.
+Mnoho webových stránek používá sledovací URL ke sledování kliknutí před přesměrováním na skutečný cíl. Tyto URL obsahují marketingové parametry a analytické tokeny, které lze odstranit, aby se zvýšila ochrana osobních údajů.
-Below is an example of how to obtain the clean destination link to bypass tracking websites and go directly to the destination.
+Níže je uveden příklad, jak získat čistý odkaz na cíl, abyste obešli sledovací webové stránky a přešli přímo na cíl.
-In our example:
+V našem příkladu:
- 1. The initial URL (with click tracking): `https://www.aff.example.com/visit?url=https%3A%2F%2Fwww.somestore.com%2F%26referrer%3Dhttps%3A%2F%2Fwww.aff.example.com%2F%26ref%3Dref-123`
- 1. Tracking URL after decoding special characters: `https://www.aff.example.com/visit?url=https://www.somestore.com/`
- 1. The website you want to visit: `https://www.somestore.com`
+ 1. Počáteční URL (se sledováním kliknutí): `https://www.aff.example.com/visit?url=https%3A%2F%2Fwww.somestore.com%2F%26referrer%3Dhttps%3A%2F%2Fwww.aff.example.com%2F%26ref%3Dref-123`
+ 1. Sledování URL po dekódování speciálních znaků: `https://www.aff.example.com/visit?url=https://www.somestore.com/`
+ 1. Webové stránky, které chcete navštívit: `https://www.somestore.com`
-To clean the URL, we first need to decode special characters (like `%3A` → `:`, `%2F` → `/`, etc.) and extract the real URL from the tracking parameters. We will use the `$urltransform` modifier to do this. The following 4 rules replace URL-encoded symbols with their real characters:
+Abychom mohli vyčistit URL, musíme nejprve dekódovat speciální znaky (jako `%3A` → `:`, `%2F` → `/`, atd.) a získat skutečnou URL z parametrů sledování. K tomu použijeme modifikátor `$urltransform`. Následující 4 pravidla nahrazují symboly URL jejich skutečnými znaky:
`/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com\/visit\?url=/$urltransform=/%3A/:/` `/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com\/visit\?url=/$urltransform=/%2F/\//` `/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com\/visit\?url=/$urltransform=/%3F/?/` `/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com\/visit\?url=/$urltransform=/%3D/=/` `/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com\/visit\?url=/$urltransform=/%26/&/`
-After that, we need to write the rule that will block the tracking website and redirect you directly to the target address (somestore.com):
+Poté musíme napsat pravidlo, které zablokuje sledovací webovou stránku a přesměruje vás přímo na cílovou adresu (somestore.com):
`/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com\/visit\?url=/$urltransform=/^https?:\/\/(?:[a-z0-9-]+\.)*?aff\.example\.com.*url=([^&]*).*/\$1/`
-Tracking links will now be automatically cleaned up, allowing direct navigation to the destination website without tracking.
+Sledovací odkazy se nyní automaticky vyčistí a umožní přímou navigaci na cílovou webovou stránku bez sledování.
:::caution Omezení
-Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters).
+Pravidla s modifikátorem `$urltransform` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters).
:::
:::info Kompatibilita
-Rules with the `$urltransform` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.15 or later.
+Pravidla s modifikátorem `$urltransform` jsou podporována AdGuardem pro Windows, Mac, Android a Linux s [CoreLibs][] v1.15 nebo novější.
:::
#### **`noop`** {#noop-modifier}
-`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed.
+Modifikátor `noop` nedělá nic a lze jej použít pouze ke zvýšení čitelnosti pravidel. Skládá se ze sekvence znaků podtržítka (`_`) libovolné délky a může se v pravidle objevit tolikrát, kolikrát je potřeba.
**Příklady**
@@ -2933,19 +2945,19 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad
:::info Kompatibilita
-Rules with `noop` modifier are not supported by AdGuard Content Blocker.
+Pravidla s modifikátorem `noop` nejsou Blokátorem obsahu AdGuard podporována.
:::
#### **`$empty` (zastaralé)** {#empty-modifier}
-:::caution Deprecation notice
+:::caution Upozornění na vyřazení
-This modifier is deprecated in favor of the [`$redirect` modifier](#redirect-modifier). Rules with `$empty` are still supported and being converted into `$redirect=nooptext` now but the support shall be removed in the future.
+Tento modifikátor je zastaralý a nahrazuje jej modifikátor [`$redirect`](#redirect-modifier). Pravidla s `$empty` jsou stále podporována a nyní se převádějí na `$redirect=nooptext`, ale podpora bude v budoucnu odstraněna.
:::
-Usually, blocked requests look like a server error to browser. If you use `$empty` modifier, AdGuard will emulate a blank response from the server with`200 OK` status.
+Obvykle se zablokované požadavky v prohlížeči tváří jako chyba serveru. Pokud použijete modifikátor `$empty`, AdGuard bude emulovat prázdnou odpověď ze serveru se stavem `200 OK`.
**Příklady**
@@ -2953,19 +2965,19 @@ Usually, blocked requests look like a server error to browser. If you use `$empt
:::info Kompatibilita
-Rules with `$empty` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari.
+Pravidla s modifikátorem `$empty` nejsou podporována Blokátorem obsahu AdGuard, AdGuardem pro iOS a AdGuardem pro Safari.
:::
#### **`$mp4` (zastaralé)** {#mp4-modifier}
-:::caution Deprecation notice
+:::caution Upozornění na vyřazení
-This modifier is deprecated in favor of the [`$redirect` modifier](#redirect-modifier). Rules with `$mp4` are still supported and being converted into `$redirect=noopmp4-1s,media` now but the support shall be removed in the future.
+Tento modifikátor je zastaralý a nahrazuje jej modifikátor [`$redirect`](#redirect-modifier). Pravidla s `$mp4` jsou stále podporována a nyní se převádějí na `$redirect=noopmp4-1s,media`, ale podpora bude v budoucnu odstraněna.
:::
-As a response to blocked request AdGuard returns a short video placeholder.
+Jako odpověď na zablokovaný požadavek vrátí AdGuard krátký zástupný videoklip.
**Příklady**
@@ -2973,33 +2985,33 @@ As a response to blocked request AdGuard returns a short video placeholder.
:::info Kompatibilita
-Rules with `$mp4` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari.
+Pravidla s modifikátorem `$mp4` nejsou podporována Blokátorem obsahu AdGuard, AdGuardem pro iOS a AdGuardem pro Safari.
:::
### Priority pravidel {#rule-priorities}
-Each rule has its own priority, which is necessary when several rules match the request and the filtering engine needs to select one of them. Priority is measured by a positive integer.
+Každé pravidlo má svou vlastní prioritu, což je nutné v případě, že požadavku odpovídá několik pravidel a filtrovací nástroj musí vybrat jedno z nich. Priorita se měří kladným celým číslem.
:::note Kolize
-When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen.
+Pokud stejnému požadavku odpovídají dvě pravidla se stejnou prioritou, implementace filtrovacího modulu určí, které z nich bude vybráno.
:::
:::info
-The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules.
+Koncept priorit pravidel nabývá na významu ve světle Manifest V3, protože stávající pravidla je třeba převést na pravidla declarativeNetRequest.
:::
#### Výpočet priority
-To calculate priority, we've categorized modifiers into different groups. These groups are ranked based on their priority, from lowest to highest. A modifier that significantly narrows the scope of a rule adds more weight to its total priority. Conversely, if a rule applies to a broader range of requests, its priority decreases.
+Pro výpočet priority jsme modifikátory rozdělili do různých skupin. Tyto skupiny jsou seřazeny podle priority od nejnižší po nejvyšší. Modifikátor, který výrazně zužuje oblast působnosti pravidla, zvyšuje jeho celkovou prioritu. Naopak, pokud se pravidlo vztahuje na širší okruh požadavků, jeho priorita se snižuje.
-It's worth noting that there are cases where a single-parameter modifier has a higher priority than multi-parameter ones. For instance, in the case of `$domain=example.com|example.org`, a rule that includes two domains has a slightly broader effective area than a rule with one specified domain, therefore its priority is lower.
+Stojí za zmínku, že existují případy, kdy má jednoparametrový modifikátor vyšší prioritu než víceparametrový. Například v případě `$domain=example.com|example.org` má pravidlo, které zahrnuje dvě domény o něco širší oblast účinnosti než pravidlo s jednou zadanou doménou, a proto je jeho priorita nižší.
-The base priority of any rule is 1. If the calculated priority is a floating-point number, it will be **rounded up** to the smallest integer greater than or equal to the calculated priority.
+Základní priorita každého pravidla je 1. Pokud je vypočtená priorita číslo s pohyblivou řádovou čárkou, bude **zaokrouhlena nahoru** na nejmenší celé číslo větší nebo rovno vypočtené prioritě.
:::info Kompatibilita
@@ -3010,7 +3022,7 @@ The base priority of any rule is 1. If the calculated priority is a floating-poi
:::note
-Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, however, they are utilized within the engine to compute the rule priority.
+Aliasy modifikátorů (`1p`, `3p` atd.) nejsou do těchto kategorií zahrnuty, nicméně jsou v rámci enginu využívány pro výpočet priority pravidla.
:::
@@ -3029,11 +3041,11 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve
- [`$to`](#to-modifier),
- omezené [typy obsahu](#content-type-modifiers) s `~`.
-When dealing with a negated domain, app, method, or content-type, we add **1 point** for the existence of the modifier itself, regardless of the quantity of negated domains or content-types. This is because the rule's scope is already infinitely broad. Put simply, by prohibiting multiple domains, content-types, methods or apps, the scope of the rule becomes only minimally smaller.
+Při práci s negovanou doménou, aplikací, metodou nebo typem obsahu přidáváme **1 bod** za existenci samotného modifikátoru bez ohledu na množství negovaných domén nebo typů obsahu. Je to proto, že oblast působnosti tohoto pravidla je již nyní nekonečně široká. Jednoduše řečeno, zákazem více domén, typů obsahu, metod nebo aplikací se rozsah pravidla zmenší jen minimálně.
#### Definované modifikátory typu obsahu, definované metody, definovaná záhlaví, $all, $popup, specifické výjimky {#priority-category-2}
-All valid content types:
+Všechny platné typy obsahu:
@@ -3050,15 +3062,15 @@ All valid content types:
- [`$websocket`](#websocket-modifier),
- [`$xmlhttprequest`](#xmlhttprequest-modifier);
-This also includes rules that implicitly add all content types:
+Patří sem také pravidla, která implicitně přidávají všechny typy obsahu:
- [`$all`](#all-modifier);
-Or rules that implicitly add the modifier `$document`:
+Nebo pravidla, která implicitně přidávají modifikátor `$document`:
- [`$popup`](#popup-modifier);
-Or some specific exceptions that implicitly add `$document,subdocument`:
+Nebo některé speciální výjimky, které implicitně přidávají `$document,subdocument`:
@@ -3071,25 +3083,25 @@ Or some specific exceptions that implicitly add `$document,subdocument`:
- [`$specifichide`](#specifichide-modifier),
- [`$urlblock`](#urlblock-modifier);
-Or allowed methods via [`$method`](#method-modifier).
+Nebo povolené metody skrze [`$method`](#method-modifier).
-Or rules with [`$header`](#header-modifier).
+Nebo pravidla s [`$header`](#header-modifier).
-The presence of any content-type modifiers adds `(50 + 50 / N)`, where `N` is the number of modifiers present, for example: `||example.com^$image,script` will add `50 + 50 / 2 = 50 + 25 = 75` to the total weight of the rule.
+Přítomnost jakýchkoli modifikátorů typu obsahu přidává `(50 + 50 / N)`, kde `N` je např. počet přítomných modifikátorů: `||example.com^$image,skript` přidá `50 + 50 / 2 = 50 + 25 = 75` k celkové váze pravidla.
-The `$all` also belongs to this category, because it implicitly adds all content-type modifiers, e.g., `$document,subdocument,image,script,media,` + `$popup`.
+Do této kategorie patří také `$all`, protože implicitně přidává všechny modifikátory typu obsahu, např. `$document,subdocument,image,script,media,` + `$popup`.
-The `$popup` also belongs to this category, because it implicitly adds the modifier `$document`. Similarly, specific exceptions add `$document,subdocument`.
+Do této kategorie patří i `$popup`, protože implicitně přidává modifikátor `$document`. Podobně specifické výjimky přidávají `$document,subdocument`.
-If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule.
+Pokud je v pravidle s povolenými metodami modifikátor `$method`, přidává `(50 + 50 / N)`, kde `N` je počet povolených metod, např.: `||example.com^$method= GET|POST|PUT` přidává `50 + 50 / 3 = 50 + 16,6 = 67` k celkové váze pravidla.
-If there is a `$header` modifier in the rule, it adds `50`.
+Pokud je v pravidle modifikátor `$header`, přidává se `50`.
#### `$domain` nebo `$app` s povolenými doménami nebo aplikacemi {#priority-category-3}
-Specified domains through `$domain` or specified applications through `$app` add `100 + 100 / N`, where `N` is the number of modifier values for example: `||example.com^$domain=example.com|example.org|example.net` will add `100 + 100 / 3 = 134.3 = 135` or `||example.com^$app=org.example.app1|org.example.app2` will add `100 + 100 / 2 = 151` or `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` will add `100 + 100/1` ($domain part) and `100 + 100/2` ($app part), totaling `350`.
+Zadané domény prostřednictvím `$domain` nebo zadané aplikace prostřednictvím `$app` přidávají `100 + 100 / N`, kde `N` je např. počet hodnot modifikátoru: `||example.com^$domain=example.com|example.org|example.net` přidává `100 + 100 / 3 = 134,3 = 135` nebo `||example.com^$app=org.example.app1|org.example.app2` sečte `100 + 100 / 2 = 151` nebo `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` sečte `100 + 100/1` ($domain část) a `100 + 100/2` ($app část), celkem `350`.
-Modifier values that are regexps or tld will be interpreted as normal entries of the form `example.com` and counted one by one, for example: `||example.com^$domain=example.*` will add `100 + 100 / 1 = 200` or `||example.com^$domain=example.*|adguard.*` will add `100 + 100 / 2 = 150`.
+Hodnoty modifikátorů, které jsou regexp nebo tld, budou interpretovány jako normální položky ve tvaru `example.com` a budou počítány po jedné, např.: `||example.com^$domain=example.*` sečte `100 + 100 / 1 = 200` nebo `||example.com^$domain=example.*|adguard.*` sečte `100 + 100 / 2 = 150`.
#### Pravidla `$redirect` {#priority-category-6}
@@ -3098,7 +3110,7 @@ Modifier values that are regexps or tld will be interpreted as normal entries of
- [`$redirect`](#redirect-modifier),
- [`$redirect-rule`](#redirect-rule-modifier).
-Each of which adds `10^3` to rule priority.
+Každé z nich přidává `10^3` k prioritě pravidla.
#### Specifické výjimky {#priority-category-4}
@@ -3113,27 +3125,27 @@ Each of which adds `10^3` to rule priority.
- [`$specifichide`](#specifichide-modifier),
- [`$urlblock`](#urlblock-modifier);
-Each of which adds `10^4` to the priority.
+Každá z nich přidává `10^4` k prioritě.
-As well as exception with [`$document modifier`](#document-modifier): because it's an alias for `$elemhide,content,jsinject,urlblock,extension`. It will add `10^4` for each modifier from [the top list](#priority-category-4), `10^4 * 5` in total.
+Stejně jako výjimka s modifikátorem [`$document`](#document-modifier): protože je to alias pro `$elemhide,content,jsinject,urlblock,extension`. Přidá `10^4` pro každý modifikátor z [horního seznamu](#priority-category-4), celkem `10^4 * 5`.
-In addition, each of these exceptions implicitly adds the two allowed content-type modifiers `$document,subdocument`.
+Každá z těchto výjimek navíc implicitně přidává dva povolené modifikátory typu obsahu `$document,subdocument`.
#### Pravidla seznamu povolených {#priority-category-5}
-Modifier `@@` adds `10^5` to rule priority.
+Modifikátor `@@` přidává `10^5` k prioritě pravidla.
#### Pravidla `$important` {#priority-category-7}
-Modifier [`$important`](#important-modifier) adds `10^6` to rule priority.
+Modifikátor [`$important`](#important-modifier) přidává `10^6` k prioritě pravidla.
#### Pravidla, pro která není stanovena váha priority {#priority-category-extra}
-[Other modifiers](#advanced-capabilities), which are supposed to perform additional post- or pre-processing of requests, do not add anything to the rule priority.
+[Ostatní modifikátory](#advanced-capabilities), které mají provádět dodatečné následné nebo předběžné zpracování požadavků, nepřidávají nic k prioritě pravidel.
:::note
-The [`$replace`](#replace-modifier) modifier takes precedence over all blocking rules of categories 1–3, as well as exception rules from categories 3–5, **except** [`$content`](#content-modifier), because an exception with the `$content` modifier overrides all `$replace` rules.
+Modifikátor [`$replace`](#replace-modifier) má přednost před všemi pravidly blokování kategorií 1-3, stejně jako před pravidly výjimek z kategorií 3-5, **kromě** [`$content`](#content-modifier), protože výjimka s modifikátorem `$content` má přednost před všemi pravidly `$replace`.
:::
@@ -3141,43 +3153,43 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking
1. `||example.com^`
- Weight of the rule without modifiers: `1`.
+ Váha pravidla bez modifikátorů: `1`.
1. `||example.com^$match-case`
- Rule weight: base weight + weight of the modifier from [category 1](#priority-category-1): `1 + 1 = 2`.
+ Váha pravidla: základní + váha modifikátoru z [kategorie 1](#priority-category-1): `1 + 1 = 2`.
1. `||example.org^$removeparam=p`
- Rule weight: base weight + 0, since $removeparam [is not involved](#priority-category-extra) in the priority calculation: `1 + 0 = 1`.
+ Váha pravidla: základní váha + 0, protože $removeparam [není zahrnuto](#priority-category-extra) do výpočtu priority: `1 + 0 = 1`.
1. `||example.org^$document,redirect=nooptext`
- Rule weight: base weight + allowed content type, [category 3](#priority-category-3) + $redirect from [category 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`.
+ Váha pravidla: základní + povolený typ obsahu, [kategorie 3](#priority-category-3) + $redirect z [kategorie 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`.
1. `@@||example.org^$removeparam=p,document`
- Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + 0 because $removeparam [is not involved](#priority-category-extra) in the priority calculation + allowed content type, [category 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`.
+ Váha pravidla: základní váha + pravidlo seznamu povolených [kategorie 5](#priority-category-5) + 0, protože $removeparam [není zapojeno](#priority-category-extra) do výpočtu priority + povolený typ obsahu [kategorie 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`.
1. `@@||example.com/ad/*$domain=example.org|example.net,important`
- Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + important rule, [category 7](#priority-category-7) + allowed domains, [category 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`.
+ Váha pravidla: základní váha + pravidlo seznamu povolených [kategorie 5](#priority-category-5) + důležité pravidlo [kategorie 7](#priority-category-7) + povolené domény [kategorie 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`.
-1. `@@||example.org^$document` without additional modifiers is an alias for `@@||example.com^$elemhide,content,jsinject,urlblock,extension`
+1. `@@||example.org^$document` bez dalších modifikátorů je aliasem pro `@@||example.com^$elemhide,content,jsinject,urlblock,extension`
- Rule weight: base weight + specific exceptions, [category 4](#priority-category-4) + two allowed content types (document and subdocument), [category 2](#priority-category-2): `1 + 10000 * 4 + (50 + 50 / 2) = 40076`.
+ Váha pravidla: základní váha + specifické výjimky, [kategorie 4](#priority-category-4) + dva povolené typy obsahu (dokument a subdokument) [kategorie 2](#priority-category-2): `1 + 10000 * 4 + (50 + 50 / 2) = 40076`.
1. `*$script,domain=a.com,denyallow=x.com|y.com`
- Rule weight: base weight + allowed content type, [category 2](#priority-category-2) + allowed domain, [category 3](#priority-category-3) + denyallow, [category 1](#priority-category-1): `1 + (50 + 50/1) + (100 + 100 / 1) + 1 = 303`.
+ Váha pravidla: základní váha + povolený typ obsahu [kategorie 2](#priority-category-2) + povolená doména, [kategorie 3](#priority-category-3) + denyallow [kategorie 1](#priority-category-1): `1 + (50 + 50/1) + (100 + 100 / 1) + 1 = 303`.
-1. `||example.com^$all` — alias to `||example.com^$document,subdocument,image,script,media,etc. + $popup`
+1. `||example.com^$all` — alias na `||example.com^$document,subdocument,image,script,media,etc. + $popup`
- Rule weight: base weight + popup ([category 1](#priority-category-1)) + allowed content types ([category 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`.
+ Váha pravidla: základní váha + vyskakovací okno ([kategorie 1](#priority-category-1)) + povolené typy obsahu ([kategorie 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`.
## Ostatní pravidla {#non-basic-rules}
-However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose.
+Základní pravidla však nemusí k blokování reklam stačit. Někdy potřebujete skrýt prvek nebo změnit část kódu HTML webové stránky, aniž byste cokoli porušili. Pravidla popsaná v této části jsou vytvořena speciálně pro tento účel.
| Kategorie \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] |
| ---------------------------------------- |:----------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:|
@@ -3199,15 +3211,15 @@ However, basic rules may not be enough to block ads. Sometimes you need to hide
:::info
-Work with non-basic rules requires the basic knowledge of HTML and CSS. So, if you want to learn how to make such rules, we recommend to get acquainted with [this documentation](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/What_is_CSS).
+Práce s ostatními pravidly vyžaduje základní znalost HTML a CSS. Pokud se tedy chcete naučit, jak taková pravidla vytvářet, doporučujeme seznámit se s touto [dokumentací](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/What_is_CSS).
:::
### Pravidla pro skrytí prvků {#cosmetic-elemhide-rules}
-Element hiding rules are used to hide the elements of web pages. It is similar to applying `{ display: none; }` style to selected element.
+Pravidla pro skrytí prvků slouží ke skrývání prvků webových stránek. Je to podobné jako použít styl `{ display: none; }` na vybraný prvek.
-Element hiding rules may operate differently [depending on the platform](#cosmetic-rules-priority).
+Pravidla pro skrytí prvků mohou fungovat odlišně [v závislosti na platformě](#cosmetic-rules-priority).
#### Syntaxe
@@ -3219,17 +3231,17 @@ domains = [domain0, domain1[, ...[, domainN]]]
- **`selektor`** — [CSS selektor](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors) definuje prvky, které mají být skryty.
- **`domains`** — omezení domény pro dané pravidlo.
-If you want to limit the rule application area to certain domains, just enter them separated with commas. For example: `example.org,example.com##selector`.
+Pokud chcete omezit oblast použití pravidel na určité domény, stačí je zadat oddělené čárkami. Např.: `example.org,example.com##selector`.
-This rule will be also applied to all subdomains of `example.org` and `example.com`.
+Toto pravidlo bude také použito na všechny subdomény `example.org` a `example.com`.
-Pokud chcete, aby se pravidlo nevztahovalo na určité domény, začněte název domény znakem `~`. For example: `~example.org##selector`.
+Pokud chcete, aby se pravidlo nevztahovalo na určité domény, začněte název domény znakem `~`. Např.: `~example.org##selector`.
-You can use both approaches in a single rule. For example, `example.org,~subdomain.example.org##domain` will work for `example.org` and all subdomains, **except `subdomain.example.org`**.
+V jednom pravidle můžete použít oba přístupy. Např. `example.org,~subdomain.example.org##domain` bude fungovat pro `example.org` a všechny subdomény **kromě `subdomain.example.org`**.
:::note
-Element hiding rules are not dependent on each other. If there is a rule `example.org##selector` in the filter and you add `~example.org##selector` both rules will be applied independently.
+Pravidla pro skrývání prvků na sobě nejsou závislá. Pokud je ve filtru pravidlo `example.org##selector` a přidáte `~example.org##selector`, budou obě pravidla použita nezávisle.
:::
@@ -3241,41 +3253,41 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl
**Omezení**
-Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari.
+Safari nepodporuje povolené i zakázané domény. Takže pravidla jako `example.org,~foo.example.org##.textad` jsou v AdGuardu pro Safari neplatná.
**Výjimky**
-Exceptions can disable some rules on particular domains. They are very similar to usual exception rules, but instead of `##` you have to use `#@#`.
+Výjimky mohou zakázat některá pravidla pro určité domény. Jsou velmi podobné běžným pravidlům výjimek, ale namísto `##` musíte použít `#@#`.
-For example, there is a rule in filter:
+Ve filtru je např. pravidlo:
```adblock
##.textad
```
-If you want to disable it for `example.com`, you can create an exception rule:
+Pokud to chcete zakázat pro `example.com`, můžete vytvořit pravidlo výjimky:
```adblock
example.com#@#.textad
```
-Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. It will completely disable matching CSS elemhide rule on ALL domains:
+Někdy může být nutné zakázat všechna pravidla omezení. Např. k provádění testů. Za tímto účelem použijte pravidlo výjimky bez zadání domény. Úplně zakáže odpovídající pravidlo CSS elemhide na VŠECH doménách:
```adblock
#@#.textad
```
-The same can be achieved by adding this rule:
+Toho lze dosáhnout přidáním tohoto pravidla:
```adblock
*#@#.textad
```
-We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions.
+Tento druh výjimek doporučujeme používat pouze v případě, že není možné změnit samotné pravidlo skrývání. V ostatních případech je lepší změnit původní pravidlo pomocí omezení domény.
### Pravidla CSS {#cosmetic-css-rules}
-Sometimes, simple hiding of an element is not enough to deal with advertising. For example, blocking an advertising element can just break the page layout. In this case AdGuard can use rules that are much more flexible than hiding rules. With these rules you can basically add any CSS styles to the page.
+Někdy pouhé skrytí prvku k vyřešení reklamy nestačí. Např. zablokování prvku reklamy může jen narušit rozvržení stránky. V tomto případě může AdGuard použít pravidla, která jsou mnohem flexibilnější než pravidla pro skrývání. Pomocí těchto pravidel můžete v podstatě přidat na stránku libovolné styly CSS.
**Syntaxe**
@@ -3294,37 +3306,57 @@ domains = [domain0, domain1[, ...[, domainN]]]
example.com#$#body { background-color: #333!important; }
```
-This rule will apply a style `background-color: #333!important;` to the `body` element at `example.com` and all subdomains.
+Toto pravidlo použije styl `background-color: #333!important;` na prvek `body` na doménu `example.com` a všechny subdomény.
**Výjimky**
-Just like with element hiding, there is a type of rules that disable the selected CSS style rule for particular domains. Exception rule syntax is almost the same, you just have to change `#$#` to `#@$#`.
+Stejně jako u skrývání prvků existuje typ pravidel, který zakáže vybrané pravidlo stylu CSS pro určité domény. Syntaxe pravidel pro výjimky je téměř stejná, stačí jen změnit `#$#` na `#@$#`.
-For example, there is a rule in filter:
+Ve filtru je např. pravidlo:
```adblock
#$#.textad { visibility: hidden; }
```
-If you want to disable it for `example.com`, you can create an exception rule:
+Pokud to chcete zakázat pro `example.com`, můžete vytvořit pravidlo výjimky:
```adblock
example.com#@$#.textad { visibility: hidden; }
```
-We recommend to use this kind of exceptions only if it is not possible to change the CSS rule itself. In other cases it is better to change the original rule, using domain restrictions.
+Tento druh výjimek doporučujeme používat pouze v případě, že není možné změnit samotné pravidlo CSS. V ostatních případech je lepší změnit původní pravidlo pomocí omezení domény.
:::caution Omezení
-Styles that lead to loading any resource are forbidden. Basically, it means that you cannot use any `` type of value in the style.
+Styly, které vedou k načtení jakéhokoli zdroje, jsou zakázány. V podstatě to znamená, že ve stylu nelze použít žádný typ hodnoty ``.
:::
:::info Kompatibilita
-CSS rules are not supported by AdGuard Content Blocker.
+Pravidla CSS nejsou Blokátorem obsahu AdGuard podporována.
-CSS rules may operate differently [depending on the platform](#cosmetic-rules-priority).
+Pravidla CSS mohou fungovat odlišně [v závislosti na platformě](#cosmetic-rules-priority).
+
+:::
+
+:::info Kompatibilita s Adblock Plus
+
+V produktech AdGuardu, které používají **CoreLibs verze 1.18 nebo novější**, můžete také použít pravidla pro skrytí prvků k vložení deklarace `remove: true`:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+Toto použití se nedoporučuje, protože je lepší používat [pravidla CSS](#cosmetic-css-rules), a je podporováno pouze z důvodu kompatibility se seznamy filtrů napsanými pro Adblock Plus.
+
+Výjimky skrytí prvků (`#@#`) jsou porovnávány pouze podle části selektoru, přičemž část bloku deklarací je ignorována. Například výše uvedené pravidlo lze deaktivovat pomocí kterékoli z následujících výjimek:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
:::
@@ -3344,30 +3376,30 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
- [Pseudo-třída `:not()`](#extended-css-not)
- [Pseudo-třída `:if-not()` (odstraněno)](#extended-css-if-not)
-CSS 3.0 is not always enough to block ads. To solve this problem AdGuard extends CSS capabilities by adding support for the new pseudo-elements. We have developed a separate [open-source library](https://github.com/AdguardTeam/ExtendedCss) for non-standard element selecting and applying CSS styles with extended properties.
+CSS 3.0 ne vždy stačí k blokování reklam. AdGuard tento problém řeší rozšířením možností CSS o podporu nových pseudo-prvků. Vyvinuli jsme samostatnou [open-source knihovnu](https://github.com/AdguardTeam/ExtendedCss) pro výběr nestandardních prvků a aplikaci CSS stylů s rozšířenými vlastnostmi.
-The idea of extended capabilities is an opportunity to match DOM elements with selectors based on their own representation (style, text content, etc.) or relations with other elements. There is also an opportunity to apply styles with non-standard CSS properties.
+Myšlenkou rozšířených možností je možnost přiřazovat prvky DOM pomocí selektorů na základě jejich vlastní reprezentace (styl, textový obsah atd.) nebo vztahů s jinými prvky. Existuje také možnost použít styly s nestandardními vlastnostmi CSS.
-**Application area**
+**Oblast použití**
-Extended selectors can be used in any cosmetic rule, whether they are [element hiding rules](#cosmetic-elemhide-rules) or [CSS rules](#cosmetic-css-rules).
+Rozšířené selektory lze použít v jakémkoli kosmetickém pravidle, ať už se jedná o pravidla pro [skrytí prvků](#cosmetic-elemhide-rules) nebo [pravidla CSS](#cosmetic-css-rules).
:::info Kompatibilita
-Rules with extended CSS selectors are not supported by AdGuard Content Blocker.
+Pravidla se selektory CSS nejsou Blokátorem obsahu AdGuard podporována.
:::
**Syntaxe**
-Regardless of the CSS pseudo-classes you are using in the rule, you can use special markers to force applying these rules by ExtendedCss. It is recommended to use these markers for all extended CSS cosmetic rules so that it was easier to find them.
+Bez ohledu na pseudo-třídy CSS, které v pravidle používáte, můžete pomocí speciálních znaků vynutit použití těchto pravidel pomocí ExtendedCss. Doporučujeme používat tyto znaky pro všechna rozšířená kosmetická pravidla CSS, aby bylo snazší je najít.
-The syntax for extended CSS rules:
+Syntaxe rozšířených pravidel CSS:
- `#?#` — pro skrytí prvku, `#@?#` — pro výjimky
- `#$?#` — pro pravidlo CSS, `#@$?#` — pro výjimky
-We **strongly recommend** using these markers any time when you use an extended CSS selector.
+**Důrazně doporučujeme** použít tyto znaky kdykoli, když používáte rozšířený selektor CSS.
**Příklady**
@@ -3376,49 +3408,49 @@ We **strongly recommend** using these markers any time when you use an extended
- `example.net#?#.banner:matches-css(width: 360px)` — toto pravidlo blokuje všechny prvky `.banner` s vlastností stylu `width: 360px`. Pravidlo platí pouze pro `example.net` a její subdomény.
- `example.net#@?#.banner:matches-css(width: 360px)` — toto pravidlo zakáže předchozí pravidlo.
-You can apply standard CSS selectors using the ExtendedCss library by using the rule marker `#?#`, e.g. `#?#div.banner`.
+Standardní CSS selektory můžete použít pomocí knihovny ExtendedCss pomocí znaku pravidla `#?#`, např. `#?#div.banner`.
-Learn more about [how to debug extended selectors](#selectors-debugging-mode).
+Přečtěte si další informace o [ladění rozšířených selektorů](#selectors-debugging-mode).
:::note
-Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious.
+Některé pseudo-třídy před sebou selektor nevyžadují. Přesto přidání [univerzálního selektoru](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` usnadňuje čtení rozšířeného selektoru, i když nemá žádný vliv na chování při porovnávání. Takže selektor `#blok :has(> .inner)` funguje přesně jako `#blok *:has(> .inner)`, ale druhý je zřejmější.
-Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly.
+Názvy pseudo-tříd nerozlišují malá a velká písmena, např. `:HAS()` funguje jako `:has()`. Přesto se běžně používají názvy s malými písmeny.
:::
#### Limitace ExtendedCss {#extended-css-limitations}
-1. CSS [comments](https://developer.mozilla.org/en-US/docs/Web/CSS/Comments) and [at-rules](https://developer.mozilla.org/en-US/docs/Web/CSS/At-rule) are not supported.
+1. CSS [komentáře](https://developer.mozilla.org/en-US/docs/Web/CSS/Comments) a [at-pravidla](https://developer.mozilla.org/en-US/docs/Web/CSS/At-rule) nejsou podporovány.
-2. Specific pseudo-class may have its own limitations: [`:has()`](#extended-css-has-limitations), [`:xpath()`](#extended-css-xpath-limitations), [`:nth-ancestor()`](#extended-css-nth-ancestor-limitations), [`:upward()`](#extended-css-upward-limitations), [`:is()`](#extended-css-is-limitations), [`:not()`](#extended-css-not-limitations), and [`:remove()`](#extended-css-remove-limitations).
+2. Konkrétní pseudot-řída může mít svá vlastní omezení: [`:has()`](#extended-css-has-limitations), [`:xpath()`](#extended-css-xpath-limitations), [`:nth-ancestor()`](#extended-css-nth-ancestor-limitations), [`:upward()`](#extended-css-upward-limitations), [`:is()`](#extended-css-is-limitations), [`:not()`](#extended-css-not-limitations) a [`:remove()`](#extended-css-remove-limitations).
#### Pseudo-třída `:has()` {#extended-css-has}
-Draft CSS 4.0 specification describes the [`:has()` pseudo-class](https://www.w3.org/TR/selectors-4/#relational). Unfortunately, [it is not yet supported](https://caniuse.com/css-has) by all popular browsers.
+Návrh specifikace CSS 4.0 popisuje [`:has()` pseudo-třídu](https://www.w3.org/TR/selectors-4/#relational). Bohužel [to zatím není podporováno](https://caniuse.com/css-has) všemi oblíbenými prohlížeči.
:::note
-Rules with the `:has()` pseudo-class must use the [native implementation of `:has()`][native-has] if they use the `##` rule marker and if it is possible, i.e., there are no other extended CSS selectors inside. If it is not supported by the product, ExtendedCss implementation will be used even for rules with the `##` marker.
+Pravidla s pseudo-třídou `:has()` musí používat nativní implementaci [ `:has()`][native-has], pokud používají znak `##` a pokud je to možné, tj. bez dalších rozšířených selektorů uvnitř. Pokud není produktem podporována, bude implementace ExtendedCss použita i pro pravidla se značkou `##`.
-Currently, not all AdGuard products support the native implementation of `:has()` yet:
+V současné době ne všechny produkty AdGuardu podporují nativní implementaci `:has()`:
- AdGuard pro Windows, AdGuard pro Mac, AdGuard pro Android a AdGuard pro Linux to **podporují** s [knihovnou CoreLibs][] v1.12 nebo novější.
- AdGuard pro iOS a AdGuard pro Safari to **podporují** s [knihovnou SafariConverterLib](#safari-converter-lib) v2.0.39 a [prohlížečem Safari v16.4][safari-16.4].
- Rozšíření prohlížeče AdGuard to zatím **nepodporuje**, ale [plánuje se][AdguardBrowserExtension#2587].
-To force the ExtendedCss implementation of `:has()` to be used, use the `#?#` or `#$?#` rule markers explicitly, e.g., `example.com#?#p:has(> a)` or `example.com#$?#div:has(> span) { display: none !important; }`.
+Chcete-li vynutit použití implementace ExtendedCss `:has()`, použijte explicitně značky pravidel `#?#` nebo `#$?#`, např. `example.com#?#p:has(> a)` nebo `example.com#$?#div:has(> span) { display: none !important; }`.
:::
-**Compatibility with other pseudo-classes**
+**Kompatibilita s jinými pseudo-třídami**
-Synonyms `:-abp-has()` is supported by ExtendedCss for better compatibility.
+Synonyma `:-abp-has()` podporují ExtendedCss pro lepší kompatibilitu.
:::danger Upozornění na odstranění
-`:if()` is no longer supported as a synonym for `:has()`.
+`:if()` již není podporováno jako synonymum pro `:has()`.
:::
@@ -3431,24 +3463,24 @@ Synonyms `:-abp-has()` is supported by ExtendedCss for better compatibility.
- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku
- `selector` — povinný, standardní nebo rozšířený selektor CSS
-The pseudo-class `:has()` selects the `target` elements that fit to the `selector`. Also the `selector` can start with a combinator.
+Pseudo-třída `:has()` vybere prvky `target`, které se hodí do `selector`. Také `selector` může začínat kombinátorem.
-A selector list can be set in `selector` as well. In this case **all** selectors in the list are being matched for now. In the future it will be fixed for [``](https://www.w3.org/TR/selectors-4/#typedef-forgiving-relative-selector-list) as argument.
+Seznam selektorů lze nastavit také v `selector`. V tomto případě se zatím porovnávají **všechny** selektory v seznamu. V budoucnu bude opraveno pro [``](https://www.w3.org/TR/selectors-4/#typedef-forgiving-relative-selector-list) jako argument.
##### `:has()` limitations {#extended-css-has-limitations}
-Usage of the `:has()` pseudo-class is [restricted for some cases (2, 3)](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54):
+Použití pseudo-třídy `:has()` je v [některých případech omezeno (2, 3)](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54):
- zakazuje `:has()` uvnitř pseudo akceptující pouze složené selektory;
- zakazuje `:has()` po běžných pseudoprvcích.
-Native `:has()` pseudo-class does not allow `:has()`, `:is()`, `:where()` inside `:has()` argument to avoid increasing the `:has()` invalidation complexity ([case 1](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54)). But ExtendedCss did not have such limitation earlier and filter lists already contain such rules, so we have not added this limitation to ExtendedCss and allow to use `:has()` inside `:has()` as it was possible before. To use it, just force ExtendedCss usage by setting `#?#`/`#$?#` rule marker.
+Nativní pseudo-třída `:has()` neumožňuje použití argumentů `:has()`, `:is()`, `:where()` uvnitř argumentu `:has()`, aby se nezvyšovala složitost zneplatnění `:has()`[(případ 1](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54)). ExtendedCss však dříve takové omezení nemělo a seznamy filtrů již taková pravidla obsahují, proto jsme toto omezení do ExtendedCss nepřidali a umožnili jsme používat `:has()` uvnitř `:has()`, jak to bylo možné dříve. Chcete-li to použít, stačí vynutit použití ExtendedCss nastavením znaku pravidla `#?#`/`#$?#`.
-Native implementation does not allow any usage of `:scope` inside the `:has()` argument ([[1]](https://github.com/w3c/csswg-drafts/issues/7211), [[2]](https://github.com/w3c/csswg-drafts/issues/6399)). Still, there are some such rules in filter lists: `div:has(:scope a)` which we continue to support by simply converting them to `div:has(> a)`, as it used to be done previously.
+Nativní implementace neumožňuje žádné použití `:scope` uvnitř argumentu `:has()` ([[1]](https://github.com/w3c/csswg-drafts/issues/7211), [[2]](https://github.com/w3c/csswg-drafts/issues/6399)). Přesto v seznamech filtrů některá taková pravidla existují: `div:has(:scope a)`, která nadále podporujeme tím, že je jednoduše převedeme na `div:has(> a)`, jak se to dělalo dříve.
**Příklady**
-`div:has(.banner)` selects all `div` elements which **include** an element with the `banner` class:
+`div:has(.banner)` vybere všechny prvky `div`, které **obsahují** prvek se třídou `banner`:
```html
@@ -3458,7 +3490,7 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a
```
-`div:has(> .banner)` selects all `div` elements which **include** an `banner` class element as a *direct child* of `div`:
+`div:has(> .banner)` vybere všechny `prvky div`, které **obsahují prvek třídy** `banner` jako *přímý potomek* z `div`:
```html
@@ -3468,7 +3500,7 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a
```
-`div:has(+ .banner)` selects all `div` elements **preceding** `banner` class element which *immediately follows* the `div` and both are children of the same parent:
+`div:has(+ .banner)` vybere všechny prvky `div` **předcházející** prvek třídy `banner`, který *bezprostředně následuje* po `div` a oba jsou potomky stejného rodu:
```html
@@ -3478,7 +3510,7 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a
Not selected
```
-`div:has(~ .banner)` selects all `div` elements **preceding** `banner` class element which *follows* the `div` but *not necessarily immediately* and both are children of the same parent:
+`div:has(~ .banner)` vybere všechny prvky `div` **předcházející** prvek třídy `banner`, který *následuje* `div`, ale *ne nutně bezprostředně* a oba jsou potomky stejného rodu:
```html
@@ -3488,7 +3520,7 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a
general sibling
```
-`div:has(span, .banner)` selects all `div` elements which **include both** `span` element and `banner` class element:
+`div:has(span, .banner)` vybere všechny prvky `div`, které **obsahují** prvek se třídou `span` a `banner`:
```html
@@ -3499,25 +3531,25 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a
```
-:::danger Old syntax
+:::danger Stará syntaxe
-[Backward compatible syntax for `:has()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-has) is supported but **not recommended**.
+[Zpětně kompatibilní syntaxe pro `:has()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-has)je podporována, ale **není doporučena**.
:::
#### Pseudo-třída `:contains()` {#extended-css-contains}
-The `:contains()` pseudo-class principle is very simple: it allows to select the elements that contain specified text or which content matches a specified regular expression. Regexp flags are supported.
+Princip pseudo-třídy `:contains()` je velmi jednoduchý: umožňuje vybrat prvky, které obsahují zadaný text nebo jejichž obsah odpovídá zadanému regulárnímu výrazu. Příznaky regexp jsou podporovány.
:::note
-The `:contains()` pseudo-class uses the `textContent` element property for matching, not the `innerHTML`.
+Pseudo-třída `:contains()` používá pro porovnávání vlastnost prvku `textContent`, nikoliv `innerHTML`.
:::
-**Compatibility with other pseudo-classes**
+**Kompatibilita s jinými pseudo-třídami**
-Synonyms `:-abp-contains()` and `:has-text()` are supported for better compatibility.
+Pro lepší kompatibilitu jsou podporována synonyma `:-abp-contains()` a `:has-text()`.
**Syntaxe**
@@ -3530,7 +3562,7 @@ Synonyms `:-abp-contains()` and `:has-text()` are supported for better compatibi
**Příklady**
-For such DOM:
+Pro DOM:
```html
@@ -3539,34 +3571,34 @@ For such DOM:
```
-the element `div#match` can be selected by any of these extended selectors:
+prvek `div#match` lze vybrat pomocí kteréhokoli z těchto rozšířených selektorů:
```adblock
-! plain text
+! prostý text
div:contains(banner)
-! regular expression
+! regulární výraz
div:contains(/as .*banner/)
-! regular expression with flags
+! regulární výraz s příznaky
div:contains(/it .*banner/gi)
```
:::note
-Only the `div` with `id=match` is selected because the next element does not contain any text, and `banner` is a part of code, not a text.
+Vybrán je pouze `div` s `id=match`, protože další prvek neobsahuje žádný text a `banner` je součástí kódu, nikoli textu.
:::
-:::danger Old syntax
+:::danger Stará syntaxe
-[Backward compatible syntax for `:contains()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-contains) is supported but **not recommended**.
+[Zpětně kompatibilní syntaxe pro `:contains()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-contains)je podporována, ale **není doporučena**.
:::
#### Pseudo-třída `:matches-css()` {#extended-css-matches-css}
-The `:matches-css()` pseudo-class allows to match the element by its current style properties. The work of the pseudo-class is based on using the [`Window.getComputedStyle()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle) method.
+Pseudo-třída `:matches-css()` umožňuje porovnat prvek podle jeho aktuálních vlastností stylu. Práce pseudo-třídy je založena na použití metody [`Window.getComputedStyle().`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle).
**Syntaxe**
@@ -3579,15 +3611,15 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty
- `property` — povinný, název vlastnosti CSS, pro kterou se má prvek zkontrolovat
- `pattern` — povinný, vzor hodnoty, který používá stejnou jednoduchou shodu se zástupnými znaky jako v základních pravidlech filtrování adres URL nebo regulární výraz. Při tomto typu porovnávání, AdGuard vždy porovnává bez ohledu na velikost písmen. V případě regulárního výrazu vypadá vzor takto: `/regexp/`.
-**Special characters escaping and unescaping**
+**Speciální znaky uvozené a neuvozené**
-For **non-regexp** patterns `(`,`)`,`[`,`]` must be **unescaped**, e.g. `:matches-css(background-image:url(data:*))`.
+Všechny vzory **non-regexp** `(`,`)`,`[`,`]` musí být **neuvozeny**, např. `:matches-css(background-image:url(data:*))`.
-For **regexp** patterns `\` should be **escaped**, e.g. `:matches-css(background-image: /^url\\("data:image\\/gif;base64.+/)`.
+Vzory **regexp** `\` by měly být **uvozeny**, např. `:matches-css(background-image: /^url\\("data:image\\/gif;base64.+/)`.
**Příklady**
-For such DOM:
+Pro DOM:
```html
@@ -3600,7 +3632,7 @@ For such DOM:
```
-the `div` elements with pseudo-element `::before` and with specified `content` property can be selected by any of these extended selectors:
+prvky `div` s pseudoprvkem `::before` a se zadanou vlastností `content` lze vybrat kterýmkoli z těchto rozšířených selektorů:
```adblock
! string pattern
@@ -3615,25 +3647,25 @@ div:matches-css(before, content: /block me/)
:::caution Omezení
-Regexp patterns **do not support** flags.
+Vzory regexp **nepodporují** příznaky.
:::
:::info Kompatibilita
-Obsolete pseudo-classes `:matches-css-before()` and `:matches-css-after()` are no longer recommended but still are supported for better compatibility.
+Zastaralé pseudo-třídy `:matches-css-before()` a `:matches-css-after()` se již nedoporučují, ale stále jsou podporovány kvůli lepší kompatibilitě.
:::
-:::danger Old syntax
+:::danger Stará syntaxe
-[Backward compatible syntax for `:matches-css()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-matches-css) is supported but **not recommended**.
+[Zpětně kompatibilní syntaxe pro `:matches-css()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-matches-css) je podporována, ale **nedoporučuje se**.
:::
#### Pseudo-třída `:matches-attr()` {#extended-css-matches-attr}
-The `:matches-attr()` pseudo-class allows selecting an element by its attributes, especially if they are randomized.
+Pseudo-třída `:matches-attr()` umožňuje vybrat prvek podle jeho atributů, zejména pokud jsou náhodné.
**Syntaxe**
@@ -3645,34 +3677,34 @@ The `:matches-attr()` pseudo-class allows selecting an element by its attributes
- `name` — povinný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro shodu názvu atributu
- `value` — volitelný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro shodu hodnoty atributu
-**Escaping special characters**
+**Uvození speciálních znaků**
-For **regexp** patterns `"` and `\` should be **escaped**, e.g. `div:matches-attr(class=/[\\w]{5}/)`.
+Pro vzory **regexp** `"` a `\` by mělo být **uvozeno**, např. `div:matches-attr(class=/[\\w]{5}/)`.
**Příklady**
-`div:matches-attr("ad-link")` selects the element `div#target1`:
+`div:matches-attr("ad-link")` vybere prvek `div#target1`:
```html
```
-`div:matches-attr("data-*"="adBanner")` selects the element `div#target2`:
+`div:matches-attr("data-*"="adBanner")` vybere prvek `div#target2`:
```html
```
-`div:matches-attr(*unit*=/^click$/)` selects the element `div#target3`:
+`div:matches-attr(*unit*=/^click$/)` vybere prvek `div#target3`:
```html
```
-`*:matches-attr("/.{5,}delay$/"="/^[0-9]*$/")` selects the element `#target4`:
+`*:matches-attr("/.{5,}delay$/"="/^[0-9]*$/")` vybere prvek `#target4`:
```html
@@ -3683,13 +3715,13 @@ For **regexp** patterns `"` and `\` should be **escaped**, e.g. `div:matches-att
:::caution Omezení
-Regexp patterns **do not support** flags.
+Vzory regexp **nepodporují** příznaky.
:::
#### Pseudo-třída `:matches-property()` {#extended-css-property}
-The `:matches-property()` pseudo-class allows selecting an element by matching its properties.
+Pseudo-třída `:matches-property()` umožňuje vybrat prvek podle jeho vlastností.
**Syntaxe**
@@ -3701,19 +3733,19 @@ The `:matches-property()` pseudo-class allows selecting an element by matching i
- `name` — povinný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro porovnávání názvů vlastností prvků
- `value` — volitelný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro porovnávání názvů vlastností prvků
-**Escaping special characters**
+**Uvození speciálních znaků**
-For **regexp** patterns `"` and `\` must be escaped, e.g. `div:matches-property(prop=/[\\w]{4}/)`.
+Pro vzory **regexp** `"` a `\` musí být uvozeno, např. `div:matches-property(prop=/[\\w]{4}/)`.
:::note
-Regexp patterns are supported in `name` for any property in chain, e.g. `prop./^unit[\\d]{4}$/.type`.
+Vzory regexp jsou podporovány v `name` pro libovolnou vlastnost v řetězci, např. `prop./^unit[\\d]{4}$/.type`.
:::
**Příklady**
-An element with such properties:
+Prvek s těmito vlastnostmi:
```javascript
divProperties = {
@@ -3733,7 +3765,7 @@ divProperties = {
};
```
-can be selected by any of these extended selectors:
+lze vybrat pomocí některého z těchto rozšířených selektorů:
```adblock
div:matches-property(check.track)
@@ -3747,24 +3779,24 @@ div:matches-property(memoizedProps.key="null")
div:matches-property(memoizedProps._owner.src=/ad/)
```
-:::tip For filter maintainers
+:::tip Pro správce filtrů
-To check properties of a specific element, do the following:
+Chcete-li zkontrolovat vlastnosti konkrétního prvku, postupujte takto:
-1. Inspect the page element or select it in `Elements` tab of browser DevTools
-1. Run `console.dir($0)` in `Console` tab
+1. Zkontrolujte prvek stránky nebo jej vyberte na kartě `Elements` v nástroji DevTools prohlížeče
+1. Spusťte `console.dir($0)` na kartě `Console`
:::
:::caution Omezení
-Regexp patterns **do not support** flags.
+Vzory regexp **nepodporují** příznaky.
:::
#### Pseudo-třída `:xpath()` {#extended-css-xpath}
-The `:xpath()` pseudo-class allows selecting an element by evaluating an XPath expression.
+Pseudo-třída `:xpath()` umožňuje vybrat prvek vyhodnocením výrazu XPath.
**Syntaxe**
@@ -3777,22 +3809,22 @@ The `:xpath()` pseudo-class allows selecting an element by evaluating an XPath e
##### `:xpath()` limitations {#extended-css-xpath-limitations}
-`target` can be omitted so it is optional. For any other pseudo-class that would mean "apply to *all* DOM nodes", but in case of `:xpath()` it just means "apply to the *whole* document", and such applying slows elements selecting significantly. That's why rules like `#?#:xpath(expression)` are limited to looking inside the `body` tag. For example, rule `#?#:xpath(//div[@data-st-area=\'Advert\'])` is parsed as `#?#body:xpath(//div[@data-st-area=\'Advert\'])`.
+`cíl` lze vynechat, takže je volitelný. Pro jakoukoli jinou pseudo-třídu by to znamenalo "aplikuj na *všechny* uzly DOM", ale v případě `:xpath()` to znamená jen "aplikuj na *celý* dokument", a takovéto použití výrazně zpomaluje výběr prvků. Proto jsou pravidla jako `#?#:xpath(expression)` omezena na nahlížení do znaku `body`. Např. pravidlo `#?#:xpath(//div[@data-st-area=\'Advert\'])` je analyzováno jako `#?#body:xpath(//div[@data-st- area=\'Advert\'])`.
-Extended selectors with defined `target` as *any* selector — `*:xpath(expression)` — can still be used but it is not recommended, so `target` should be specified instead.
+Rozšířené selektory s definovaným `target` jako *libovolný selektor* — `*:xpath(expression)` — lze stále použít, ale nedoporučuje se to, proto by měl být místo toho uveden `target`.
-Works properly only at the end of selector, except for [pseudo-class :remove()](#remove-pseudos).
+Funguje správně pouze na konci selektoru, s výjimkou [pseudo-třídy :remove()](#remove-pseudos).
**Příklady**
-`:xpath(//*[@class="banner"])` selects the element `div#target1`:
+`:xpath(//*[@class="banner"])` vybere prvek `div#target1`:
```html
```
-`:xpath(//*[@class="inner"]/..)` selects the element `div#target2`:
+`:xpath(//*[@class="inner"]/..)` vybere prvek `div#target2`:
```html
@@ -3803,7 +3835,7 @@ Works properly only at the end of selector, except for [pseudo-class :remove()](
#### Pseudo-třída `:nth-ancestor()` {#extended-css-nth-ancestor}
-The `:nth-ancestor()` pseudo-class allows to lookup the *nth* ancestor relative to the previously selected element.
+Pseudo-třída `:nth-ancestor()` umožňuje vyhledat *nth* předka vzhledem k dříve vybranému prvku.
```text
subject:nth-ancestor(n)
@@ -3823,11 +3855,11 @@ subject:nth-ancestor(n)
##### `:nth-ancestor()` limitations {#extended-css-nth-ancestor-limitations}
-The `:nth-ancestor()` pseudo-class is not supported inside the argument of the [`:not()` pseudo-class](#extended-css-not).
+Pseudo-třída `:nth-ancestor()` není podporována v argumentu [pseudo-třídy `:not()`](#extended-css-not).
**Příklady**
-For such DOM:
+Pro DOM:
```html
@@ -3844,11 +3876,11 @@ For such DOM:
```
-`.child:nth-ancestor(1)` selects the element `div#target1`, `div[class="inner"]:nth-ancestor(3)` selects the element `div#target2`.
+`.child:nth-ancestor(1)` vybere prvek `div#target1`, `div[class="inner"]:nth-ancestor(3)` vybere prvek `div#target2`.
#### Pseudo-třída `:upward()` {#extended-css-upward}
-The `:upward()` pseudo-class allows to lookup the ancestor relative to the previously selected element.
+Pseudo-třída `:upward()` umožňuje vyhledat předka vzhledem k dříve vybranému prvku.
**Syntaxe**
@@ -3863,11 +3895,11 @@ subject:upward(ancestor)
##### `:upward()` limitations {#extended-css-upward-limitations}
-The `:upward()` pseudo-class is not supported inside the argument of the [`:not()` pseudo-class](#extended-css-not).
+Pseudo-třída `:nth-upward()` není podporována v argumentu [pseudo-třídy `:not()`](#extended-css-not).
**Příklady**
-For such DOM:
+Pro DOM:
```html
@@ -3884,13 +3916,13 @@ For such DOM:
```
-`.inner:upward(div[data])` selects the element `div#target1`, `.inner:upward(div[id])` selects the element `div#target2`, `.child:upward(1)` selects the element `div#target1`, `.inner:upward(3)` selects the element `div#target2`.
+`.inner:upward(div[data])` vybere prvek `div#target1`, `.inner:upward(div[id])` vybere prvek `div#target2`, `.child:upward(1)` vybere prvek `div#target1`, `.inner:upward(3)` vybere prvek `div#target2`.
#### Pseudo-třída `:remove()` a pseudo-vlastnost `remove` {#remove-pseudos}
-Sometimes, it is necessary to remove a matching element instead of hiding it or applying custom styles. In order to do it, you can use the `:remove()` pseudo-class as well as the `remove` pseudo-property.
+Někdy je nutné odpovídající prvek odstranit namísto jeho skrytí nebo použití vlastních stylů. Chcete-li to provést, můžete použít pseudo-třídu `:remove()` a také pseudo-vlastnost `remove`.
-**Pseudo-class `:remove()` can be placed only at the end of a selector.**
+**Pseudo-třídu `:remove()` lze umístit pouze na konec selektoru.**
**Syntaxe**
@@ -3906,11 +3938,11 @@ selector { remove: true; }
##### `:remove()` a `remove` limitations {#extended-css-remove-limitations}
-The `:remove()` pseudo-class is limited to work properly only at the end of selector.
+Pseudo-třída `:remove()` je omezena tak, aby správně fungovala pouze na konci selektoru.
-For applying the `:remove()` pseudo-class to any element, the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` should be used. Otherwise such extended selector may be considered as invalid, e.g. `.banner > :remove()` is not valid for removing any child element of `banner` class element, so it should look like `.banner > *:remove()`.
+Pro použití pseudo-třídy `:remove()` na libovolný prvek je třeba použít [univerzální selektor](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`. V opačném případě může být takový rozšířený selektor považován za neplatný, např. `.banner > :remove()` neplatí pro odstranění jakéhokoli podřízeného prvku třídy `banner`, takže by měl vypadat jako `.banner > *:remove()`.
-If the `:remove()` pseudo-class or the `remove` pseudo-property is used, all style properties are ignored except for the [`debug` pseudo-property](#selectors-debug-mode).
+Pokud je použita pseudo-třída `:remove()` nebo pseudovlastnost `remove`, všechny vlastnosti stylu se ignorují kromě pseudovlastnosti [`debug`](#selectors-debug-mode).
**Příklady**
@@ -3924,13 +3956,13 @@ div[class]:has(> a > img) { remove: true; }
:::note
-Rules with the `remove` pseudo-property must use `#$?#` marker: `$` for CSS-style rule syntax, `?` for ExtendedCss syntax.
+Pravidla s pseudovlastností `remove` musí používat znak `#$?#`: `$` pro syntaxi pravidel stylu CSS, `?` pro syntaxi ExtendedCss.
:::
#### Pseudo-třída `:is()` {#extended-css-is}
-The `:is()` pseudo-class allows to match any element that can be selected by any of selectors passed to it. Invalid selectors are skipped and the pseudo-class deals with valid ones with no error thrown. Our implementation of the [native `:is()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:is).
+Pseudo-třída `:is()` umožňuje porovnat jakýkoli prvek, který lze vybrat kterýmkoli ze selektorů, které jí byly předány. Neplatné selektory jsou přeskočeny a pseudo-třída se vypořádá s platnými selektory bez vyhození chyby. Naše implementace [nativní pseudotřídy `:is()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is).
**Syntaxe**
@@ -3943,15 +3975,15 @@ The `:is()` pseudo-class allows to match any element that can be selected by any
##### `:is()` limitations {#extended-css-is-limitations}
-Rules with the `:is()` pseudo-class must use the [native implementation of `:is()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is) if rules use `##` marker and it is possible, i.e. with no other extended selectors inside. To force applying ExtendedCss rules with `:is()`, use `#?#`/`#$?#` marker explicitly.
+Pravidla s pseudo-třídou `:is()` musí používat nativní implementaci [ `:has()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is), pokud pravidla používají znak `##` a pokud je to možné, tj. bez dalších rozšířených selektorů uvnitř. Chcete-li vynutit použití pravidel ExtendedCss s `:is()`, použijte explicitně znak `#?#`/`#$?#`.
-If the `:is()` pseudo-class argument `selectors` is an extended selector, due to the way how the `:is()` pseudo-class is implemented in ExtendedCss v2.0, it is impossible to apply it to the top DOM node which is `html`, i.e. `#?#html:is()` does not work. So if `target` is not defined or defined as the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, the extended pseudo-class applying is limited to **`html`'s children**, e.g. rules `#?#:is(...)` and `#?#*:is(...)` are parsed as `#?#html *:is(...)`. Please note that there is no such limitation for a standard selector argument, i.e. `#?#html:is(.locked)` works fine.
+Pokud je argument `:is()` pseudo-třídy `selector` rozšířeným selektorem, vzhledem ke způsobu, jakým je v ExtendedCss v2.0 implementována pseudo-třída `:is()`, není možné ji použít na horní uzel DOM, kterým je `html`, tj. `#?#html:is()` nefunguje. Pokud tedy `target` není definován nebo je definován jako [univerzální selektor](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, je rozšířené použití pseudo-třídy omezeno na **`html`potomky**, např. pravidla `#?#:is(...)` a `#?#*:is(...)` jsou analyzována jako `#?#html *:is(...)`. Upozorňujeme, že pro standardní argument selektoru takové omezení neexistuje, tj. `#?#html:is(.locked)` funguje bez problémů.
-[Complex selectors](https://www.w3.org/TR/selectors-4/#complex) with extended pseudo-classes are not supported as `selectors` argument for `:is()` pseudo-class, only [compound ones](https://www.w3.org/TR/selectors-4/#compound) are allowed. Check examples below for more details.
+[Komplexní selektory](https://www.w3.org/TR/selectors-4/#complex) s rozšířenými pseudo-třídami nejsou podporovány jako argument `selector` pro pseudo-třídu `:is()`, povoleny jsou pouze [složené](https://www.w3.org/TR/selectors-4/#compound). Další podrobnosti naleznete v příkladech níže.
**Příklady**
-`#container *:is(.inner, .footer)` selects only the element `div#target1`:
+`#container *:is(.inner, .footer)` vybere pouze prvek `div#target1`:
```html
@@ -3964,7 +3996,7 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to
```
-Due to limitations `:is(*:not([class]) > .banner)'` does not work but `:is(*:not([class]):has(> .banner))` can be used instead of it to select the element `div#target2`:
+Kvůli omezením `:is(*:not([class]) > .banner)'` nefunguje, ale lze místo něj použít `:is(*:not([class]):has(> .banner))` k výběru prvku `div#target2`:
```html
@@ -3976,7 +4008,7 @@ Due to limitations `:is(*:not([class]) > .banner)'` does not work but `:is(*:not
#### Pseudo-třída `:not()` {#extended-css-not}
-The `:not()` pseudo-class allows to select elements which are *not matched* by selectors passed as argument. Invalid argument selectors are not allowed and error is to be thrown. Our implementation of the [`:not()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:not).
+Pseudo-třída `:not()` umožňuje vybrat prvky, které se *neshodují* se selektory předávanými jako argument. Neplatné selektory argumentů nejsou povoleny a je třeba vyhodit chybu. Naše implementace pseudo-třídy [`:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not).
**Syntaxe**
@@ -3989,17 +4021,17 @@ The `:not()` pseudo-class allows to select elements which are *not matched* by s
##### `:not()` limitations {#extended-css-not-limitations}
-Rules with the `:not()` pseudo-class must use the [native implementation of `:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not) if rules use `##` marker and it is possible, i.e. with no other extended selectors inside. To force applying ExtendedCss rules with `:not()`, use `#?#`/`#$?#` marker explicitly.
+Pravidla s pseudo-třídou `:not()` musí používat nativní implementaci [ `:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not), pokud pravidla používají znak `##` a pokud je to možné, tj. bez dalších rozšířených selektorů uvnitř. Chcete-li vynutit použití pravidel ExtendedCss s `:not()`, použijte explicitně znak `#?#`/`#$?#`.
-If the `:not()` pseudo-class argument `selectors` is an extended selector, due to the way how the `:not()` pseudo-class is implemented in ExtendedCss v2.0, it is impossible to apply it to the top DOM node which is `html`, i.e. `#?#html:not()` does not work. So if `target` is not defined or defined as the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, the extended pseudo-class applying is limited to **`html`'s children**, e.g. rules `#?#:not(...)` and `#?#*:not(...)` are parsed as `#?#html *:not(...)`. Please note that there is no such limitation for a standard selector argument, i.e. `#?#html:not(.locked)` works fine.
+Pokud je argument `:not()` pseudo-třídy `selector` rozšířeným selektorem, vzhledem ke způsobu, jakým je v ExtendedCss v2.0 implementována pseudo-třída `:not()`, není možné ji použít na horní uzel DOM, kterým je `html`, tj. `#?#html:not()` nefunguje. Pokud tedy `target` není definován nebo je definován jako [univerzální selektor](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, je rozšířené použití pseudo-třídy omezeno na **`html`potomky**, např. pravidla `#?#:not(...)` a `#?#*:not(...)` jsou analyzována jako `#?#html *:not(...)`. Upozorňujeme, že pro standardní argument selektoru takové omezení neexistuje, tj. `#?#html:not(.locked)` funguje bez problémů.
-The `:not()` is considered as a standard CSS pseudo-class inside the argument of the [`:upward()` pseudo-class](#extended-css-upward) because `:upward()` supports only standard selectors.
+`:not()` je považována za standardní pseudo-třídu CSS uvnitř argumentu pseudo-třídy [`:upward()`](#extended-css-upward), protože `:upward()` podporuje pouze standardní selektory.
-"Up-looking" pseudo-classes which are [`:nth-ancestor()`](#extended-css-nth-ancestor) and [`:upward()`](#extended-css-upward) are not supported inside `selectors` argument for `:not()` pseudo-class.
+"Up-looking" pseudotřídy, které jsou [`:nth-ancestor()`](#extended-css-nth-ancestor) a [`:upward()`](#extended-css-upward) nejsou podporovány uvnitř argumentu `selector` pro pseudo-třídu `:not()`.
**Příklady**
-`#container > *:not(h2, .text)` selects only the element `div#target1`:
+`#container > *:not(h2, .text)` vybere pouze prvek `div#target1`:
```html
@@ -4014,31 +4046,31 @@ The `:not()` is considered as a standard CSS pseudo-class inside the argument of
:::danger Upozornění na odstranění
-The `:if-not()` pseudo-class is removed and is no longer supported. Pravidla s tímto modifikátorem jsou považována za neplatná.
+Pseudo-třída `:if-not()` je odstraněna a již není podporována. Pravidla s tímto modifikátorem jsou považována za neplatná.
:::
-This pseudo-class was basically a shortcut for `:not(:has())`. It was supported by ExtendedCss for better compatibility with some filters subscriptions.
+Tato pseudo-třída byla v podstatě zkratkou pro `:not(:has())`. Byla podporována ExtendedCss pro lepší kompatibilitu s některými odběry filtrů.
### Přednost kosmetických pravidel {#cosmetic-rules-priority}
-The way **element hiding** and **CSS rules** are applied is platform-specific.
+Způsob, jakým jsou aplikována pravidla **pro skrývání prvků** a **CSS**, je specifický pro danou platformu.
-**In AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux**, we use a stylesheet injected into the page. The priority of cosmetic rules is the same as any other websites' CSS stylesheet. But there is a limitation: [element hiding](#cosmetic-elemhide-rules) and [CSS rules](#cosmetic-css-rules) cannot override inline styles. In such cases, it is recommended to use extended selectors or HTML filtering.
+**V aplikacích AdGuard pro Windows, AdGuard pro Mac, AdGuard pro Android a AdGuard pro Linux** používáme soubor stylů vložený do stránky. Priorita kosmetických pravidel je stejná jako u jakéhokoli jiného souboru stylů CSS na webových stránkách. Existují však omezení: [skrytí prvku](#cosmetic-elemhide-rules) a [pravidla CSS](#cosmetic-css-rules) nemohou přepsat vložené styly. V takových případech se doporučuje použít rozšířené selektory nebo filtrování HTML.
-**In AdGuard Browser Extension**, the so-called "user stylesheets" are used. They have higher priority than even the inline styles.
+**V Rozšíření prohlížeče AdGuard** se používají tzv. "soubory uživatelských stylů". Mají vyšší prioritu než řádkové styly.
-**Extended CSS selectors** use JavaScript to work and basically add an inline style themselves, therefore they can override any style.
+**Rozšířené selektory CSS** používají k práci JavaScript a v podstatě samy přidávají vložený styl, takže mohou přepsat jakýkoli styl.
## HTML pravidla filtrování {#html-filtering-rules}
-In most cases, the basis and cosmetic rules are enough to filter ads. But sometimes it is necessary to change the HTML-code of the page itself before it is loaded. This is when you need filtering rules for HTML content. They allow to indicate the HTML elements to be cut out before the browser loads the page.
+Ve většině případů stačí k filtrování reklam základní a kosmetická pravidla. Někdy je však nutné změnit kód HTML samotné stránky před jejím načtením. V takovém případě potřebujete pravidla pro filtrování obsahu HTML. Umožňují označit prvky HTML, které mají být vyříznuty před načtením stránky prohlížečem.
:::info Kompatibilita
-HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard for Linux, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level.
+Pravidla filtrování HTML podporuje AdGuard pro Windows, AdGuard pro Mac, AdGuard pro Android, AdGuard pro Linux a rozšíření prohlížeče AdGuard pro Firefox. Taková pravidla v rozšířeních pro jiné prohlížeče nefungují, protože nemohou měnit obsah na úrovni sítě.
-The syntax with an optional `value` in the attributes is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with CoreLibs v1.18 or later. It is also supported by AdGuard Browser Extension v5.2 or later. For the other products and previous versions `value` must **always** be specified. Otherwise, the rule will be treated as incorrect and ignored.
+Syntaxi s volitelnou hodnotou `value` v atributech podporuje AdGuard pro Windows, AdGuard pro Mac a AdGuard pro Android s knihovnou CoreLibs v1.18 nebo novější. Podporuje ji také rozšíření Rozšíření prohlížeče AdGuard v5.2 nebo novější. U ostatních produktů a předchozích verzí musí být **vždy** uvedena hodnota `value`. V opačném případě bude pravidlo považováno za nesprávné a bude ignorováno.
:::
@@ -4063,21 +4095,21 @@ pseudoClasses = pseudoClass *pseudoClass
### Příklady
-**HTML code:**
+**Kód HTML:**
```html
```
-**Rule:**
+**Pravidlo:**
```adblock
example.org$$script[data-src="banner"]
```
-This rule removes all `script` elements with the attribute `data-src` containing the substring `banner`. The rule applies only to `example.org` and all its subdomains.
+Toto pravidlo odstraní všechny prvky `script` s atributem `data-src` obsahujícím podřetězec `banner`. Pravidlo platí pouze pro `example.org` a všechny její subdomény.
-If the value of the attribute is omitted in the rule, then the element will be removed if it contains the specified attribute, regardless of its value. This is also the way to remove the elements whose attributes don't have any value at all.
+Pokud je hodnota atributu v pravidle vynechána, bude prvek odstraněn, pokud obsahuje zadaný atribut bez ohledu na jeho hodnotu. Tímto způsobem lze také odstranit prvky, jejichž atributy nemají vůbec žádnou hodnotu.
```html
@@ -4088,25 +4120,25 @@ If the value of the attribute is omitted in the rule, then the element will be r
example.org$$div[some_attribute]
```
-This rule removes all `div` elements with the attribute `some_attribute` on `example.org` and all its subdomains. So, the both `div` elements from the example above will be removed.
+Toto pravidlo odstraní všechny prvky `div` s atributem `some_attribute` na `example.org` a všech jejích subdoménách. Oba prvky `div` z výše uvedeného příkladu budou odstraněny.
### Speciální atributy
-In addition to usual attributes, which value is every element checked for, there is a set of special attributes that change the way a rule works. Below there is a list of these attributes:
+Kromě obvyklých atributů, jejichž hodnotu kontroluje každý prvek, existuje sada speciálních atributů, které mění způsob fungování pravidla. Níže je uveden seznam těchto atributů:
#### `tag-content`
-:::caution Deprecation notice
+:::caution Upozornění na vyřazení
-This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available.
+Tento speciální atribut může být v budoucnu nepodporován. Raději použijte pseudo-třídu `:contains()`, pokud je k dispozici.
:::
-This is the most frequently used special attribute. It limits selection with those elements whose innerHTML code contains the specified substring.
+Jedná se o nejčastěji používaný speciální atribut. Omezí výběr na ty prvky, jejichž kód innerHTML obsahuje zadaný podřetězec.
-You must use `""` to escape `"`, for instance: `$$script[tag-content="alert(""this is ad"")"]`
+Musíte použít `""` k uvození `"`>, např.: `$$script[tag-content="alert(""this is ad"")"]`
-For example, take a look at this HTML code:
+Podívejte se například na tento HTML kód:
```html
```
-Following rule will delete all `script` elements with a `banner` substring in their code:
+Následující pravidlo smaže všechny prvky `script` s podřetězcem `banner` v jejich kódu:
```adblock
$$script[tag-content="banner"]
@@ -4122,45 +4154,45 @@ $$script[tag-content="banner"]
:::caution Omezení
-The `tag-content` special attribute must not appear in a selector to the left of a `>` combinator.
+Speciální atribut `tag-content` se nesmí objevit v selektoru nalevo od kombinátoru `>`.
:::
#### `wildcard`
-:::caution Deprecation notice
+:::caution Upozornění na vyřazení
-This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available.
+Tento speciální atribut může být v budoucnu nepodporován. Raději použijte pseudo-třídu `:contains()`, pokud je k dispozici.
:::
-This special attribute works almost like `tag-content` and allows you to check the innerHTML code of the document. Rule will check if HTML code of the element fits the [search pattern](https://en.wikipedia.org/wiki/Glob_(programming)).
+Tento speciální atribut funguje téměř jako `tag-content` a umožňuje kontrolovat kód dokumentu innerHTML. Pravidlo zkontroluje, zda kód HTML prvku odpovídá [vyhledávacímu vzoru](https://en.wikipedia.org/wiki/Glob_(programming)).
-You must use `""` to escape `"`, for instance: `$$script[wildcard=""banner""]`
+Musíte použít `""` k uvození `"`>, např.: `$$script[wildcard=""banner""]`
-For example: `$$script[wildcard="*banner*text*"]`
+Např.: `$$script[wildcard="*banner*text*"]`
-It checks if the element code contains the two consecutive substrings `banner` and `text`.
+Kontroluje, zda prvek code obsahuje dva po sobě jdoucí podřetězce `banner` a `text`.
:::caution Omezení
-The `wildcard` special attribute must not appear in a selector to the left of a `>` combinator.
+Speciální atribut `wildcard` se nesmí objevit v selektoru nalevo od kombinátoru `>`.
:::
#### `max-length`
-:::caution Deprecation notice
+:::caution Upozornění na vyřazení
-This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class with a regular expression where it is available.
+Tento speciální atribut může být v budoucnu nepodporován. Raději použijte pseudotřídu `:contains()` s regulárním výrazem, pokud je k dispozici.
:::
-Specifies the maximum length for content of HTML element. If this parameter is set and the content length exceeds the value, a rule does not apply to the element.
+Určuje maximální délku obsahu prvku HTML. Pokud je tento parametr nastaven a délka obsahu přesahuje tuto hodnotu, pravidlo se na prvek nevztahuje.
-**Default value**
+**Výchozí hodnota**
-If this parameter is not specified, the `max-length` is considered to be 8192.
+Pokud tento parametr není zadán, považuje se `max-lenght` za 8192.
Např:
@@ -4168,23 +4200,23 @@ Např:
$$div[tag-content="banner"][max-length="400"]
```
-This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which does not exceed `400` characters.
+Toto pravidlo odstraní všechny prvky `div`, jejichž kód obsahuje podřetězec `banner` a jejichž délka nepřesahuje `400` znaků.
:::caution Omezení
-The `max-length` special attribute must not appear in a selector to the left of a `>` combinator.
+Speciální atribut `max-length` se nesmí objevit v selektoru nalevo od kombinátoru `>`.
:::
#### `min-length`
-:::caution Deprecation notice
+:::caution Upozornění na vyřazení
-This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class with a regular expression where it is available.
+Tento speciální atribut může být v budoucnu nepodporován. Raději použijte pseudotřídu `:contains()` s regulárním výrazem, pokud je k dispozici.
:::
-Specifies the minimum length for content of HTML element. If this parameter is set and the content length is less than preset value, a rule does not apply to the element.
+Určuje minimální délku obsahu prvku HTML. Pokud je tento parametr nastaven a délka obsahu je menší než nastavená hodnota, pravidlo se na prvek nevztahuje.
Např:
@@ -4192,11 +4224,11 @@ Např:
$$div[tag-content="banner"][min-length="400"]
```
-This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which exceeds `400` characters.
+Toto pravidlo odstraní všechny prvky `div`, jejichž kód obsahuje podřetězec `banner` a jejichž délka přesahuje `400` znaků.
:::caution Omezení
-The `min-length` special attribute must not appear in a selector to the left of a `>` combinator.
+Speciální atribut `min-length` se nesmí objevit v selektoru nalevo od kombinátoru `>`.
:::
@@ -4218,53 +4250,53 @@ nebo
:::note Kompatibilita
-`:-abp-contains()` and `:has-text()` are synonyms for `:contains()`.
+`:-abp-contains()` a `:has-text()` jsou synonyma pro `:contains()`.
:::
:::info Kompatibilita
-The `:contains()` pseudo-class is supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.13 or later.
+Pseudotřída `:contains()` je podporována aplikacemi AdGuard pro Windows, AdGuard pro Mac, AdGuard pro Android a AdGuard pro Linux s [knihovnou CoreLibs][] v1.13 nebo novější.
:::
-Requires that the inner HTML of the element contains the specified text or matches the specified regular expression.
+Vyžaduje, aby vnitřní HTML prvku obsahovalo zadaný text nebo odpovídalo zadanému regulárnímu výrazu.
:::caution Omezení
-A `:contains()` pseudo-class must not appear in a selector to the left of a `>` combinator.
+Pseudotřída `:contains()` se nesmí objevit v selektoru nalevo od kombinátoru `>`.
:::
### Výjimky
-Similar to hiding rules, there is a special type of rules that disable the selected HTML filtering rule for particular domains. The syntax is the same, you just have to change `$$` to `$@$`.
+Podobně jako u pravidel skrývání existuje speciální typ pravidel, který zakáže vybrané pravidlo filtrování HTML pro určité domény. Syntaxe je stejná, jen je třeba změnit `$$` na `$@$`.
-For example, there is a rule in filter:
+Ve filtru je např. pravidlo:
```adblock
$$script[tag-content="banner"]
```
-If you want to disable it for `example.com`, you can create an exception rule:
+Pokud to chcete zakázat pro `example.com`, můžete vytvořit pravidlo výjimky:
```adblock
example.com$@$script[tag-content="banner"]
```
-Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain.
+Někdy může být nutné zakázat všechna pravidla omezení. Např. k provádění testů. Za tímto účelem použijte pravidlo výjimky bez zadání domény.
```adblock
$@$script[tag-content="banner"]
```
-We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions.
+Tento druh výjimek doporučujeme používat pouze v případě, že není možné změnit samotné pravidlo skrývání. V ostatních případech je lepší změnit původní pravidlo pomocí omezení domény.
## Pravidla JavaScript {#javascript-rules}
-AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages.
+AdGuard podporuje speciální typ pravidel, která umožňují vložit na webové stránky libovolný kód JavaScript.
-We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used.
+**Důrazně doporučujeme** používat [skriptlety](#scriptlets) namísto pravidel JavaScript, kdykoli je to možné. Pravidla JS mají pomoci s laděním, ale jako dlouhodobé řešení by se mělo používat pravidlo skriptlet.
**Syntaxe**
@@ -4281,51 +4313,51 @@ rule = [domains] "#%#" script
**Výjimky**
-Similar to hiding rules, there is a special type of rules that disable the selected JavaScript rule for particular domains. The syntax is the same, you just have to change `#%#` to `#@%#`.
+Podobně jako u pravidel skrývání existuje speciální typ pravidel, který zakáže vybrané pravidlo JavaScript pro určité domény. Syntaxe je stejná, jen je třeba změnit `#%#` na `#@%#`.
-For example, there is a rule in filter:
+Ve filtru je např. pravidlo:
```adblock
#%#window.__gaq = undefined;
```
-If you want to disable it for `example.com`, you can create an exception rule:
+Pokud to chcete zakázat pro `example.com`, můžete vytvořit pravidlo výjimky:
```adblock
example.com#@%#window.__gaq = undefined;
```
-Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain.
+Někdy může být nutné zakázat všechna pravidla omezení. Např. k provádění testů. Za tímto účelem použijte pravidlo výjimky bez zadání domény.
```adblock
#@%#window.__gaq = undefined;
```
-We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions.
+Tento druh výjimek doporučujeme používat pouze v případě, že není možné změnit samotné pravidlo skrývání. V ostatních případech je lepší změnit původní pravidlo pomocí omezení domény.
:::caution Omezení
-JavaScript rules can only be used [**in trusted filters**](#trusted-filters).
+Typ pravidel JavaScript lze použít pouze [**v důvěryhodných filtrech**](#trusted-filters).
:::
:::info Kompatibilita
-JavaScript rules are not supported by AdGuard Content Blocker.
+Pravidla JavaScript nejsou Blokátorem obsahu AdGuard podporována.
:::
## Pravidla skriptlet {#scriptlets}
-Scriptlet is a JavaScript function that provides extended capabilities for content blocking. These functions can be used in a declarative manner in AdGuard filtering rules.
+Skriptlet je funkce JavaScript, která poskytuje rozšířené možnosti pro blokování obsahu. Tyto funkce lze v AdGuard pravidlech filtrování používat deklarativním způsobem.
:::note
-AdGuard supports a lot of different scriptlets. In order to achieve cross-blocker compatibility, we also support syntax of uBO and ABP.
+AdGuard podporuje mnoho různých skriptletů. Abychom dosáhli kompatibility mezi blokátory, podporujeme také syntaxi uBO a ABP.
:::
-**Blocking rules syntax**
+**Syntaxe pravidel blokování**
```text
[domains]#%#//scriptlet(name[, arguments])
@@ -4337,21 +4369,21 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke
**Příklady**
-1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument:
+1. Použijte skriptlet `abort-on-property-read` na všech stránkách `example.org` a jejích subdoménách a předejte mu argument `alert`:
```adblock
example.org#%#//scriptlet('abort-on-property-read', 'alert')
```
-1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains:
+1. Odstraňte třídu `branding` ze všech prvků `div[class^="inner"]` na všech stránkách `example.org` a jejích subdoménách:
```adblock
example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]')
```
-**Exception rules syntax**
+**Syntaxe pravidel pro výjimky**
-Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`:
+Pravidla výjimek mohou zakázat některé skriptlety v určitých doménách. Syntaxe pravidel skriptletů pro výjimky je podobná jako u běžných pravidel skriptletů, ale místo `#%#` se používá `#@%#`:
```text
[domains]#@%#//scriptlet([name[, arguments]])
@@ -4363,28 +4395,28 @@ Exception rules can disable some scriptlets on particular domains. The syntax fo
**Příklady**
-1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains:
+1. Zakázat specifické pravidlo skriptletu tak, aby se pouze `abort-on-property-read` použilo pouze na `example.org` a její subdomény:
```adblock
example.org,example.com#%#//scriptlet("abort-on-property-read", "alert")
example.com#@%#//scriptlet("abort-on-property-read", "alert")
```
-1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains:
+1. Zakázat všechny skriptlety `abort-on-property-read` pro `example.com` a její subdomény:
```adblock
example.org,example.com#%#//scriptlet("abort-on-property-read", "alert")
example.com#@%#//scriptlet("abort-on-property-read")
```
-1. Disable all scriptlets for `example.com` and its subdomains:
+1. Zakázat všechny skriptlety pro `example.com` a její subdomény:
```adblock
example.org,example.com#%#//scriptlet("abort-on-property-read", "alert")
example.com#@%#//scriptlet()
```
-1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains:
+1. Použijte `set-constant` a `set-cookie` na libovolnou webovou stránku, ale vzhledem ke speciálnímu pravidlu výjimky pro skriplety bude na `stránce example.org` a jejích subdoménách použito pouze `set-constant`:
```adblock
#%#//scriptlet('set-constant', 'adList', 'emptyArr')
@@ -4392,7 +4424,7 @@ Exception rules can disable some scriptlets on particular domains. The syntax fo
example.org#@%#//scriptlet('set-cookie')
```
-1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains:
+1. Použijte `adjust-setInterval` na libovolnou webovou stránku a `set-local-storage-item` na `example.com` a jejích subdoménách, ale existuje také několik pravidel pro výjimky skriptletů, takže na `example.com` a jejích subdoménách nebudou použita žádná pravidla pro skriptlety:
```adblock
#%#//scriptlet('adjust-setInterval', 'count', '*', '0.001')
@@ -4400,49 +4432,49 @@ Exception rules can disable some scriptlets on particular domains. The syntax fo
example.com#@%#//scriptlet()
```
-Learn more about [how to debug scriptlets](#debug-scriptlets).
+Další informace o [ladění skriptletů](#debug-scriptlets).
-More information about scriptlets can be found [on GitHub](https://github.com/AdguardTeam/Scriptlets#scriptlets).
+Další informace o skriptletech najdete [na GitHubu](https://github.com/AdguardTeam/Scriptlets#scriptlets).
:::info Kompatibilita
-Scriptlet rules are not supported by AdGuard Content Blocker.
+Skriplety nejsou Blokátorem obsahu AdGuard podporovány.
-The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets.
+Úplná syntaxe pravidel pro výjimky skriptletů je podporována AdGuardem pro Windows, AdGuardem pro Mac, AdGuardem pro Android a AdGuardem pro Linux s [CoreLibs][] v1.16 nebo novějšími a rozšířením prohlížeče AdGuard pro Chrome, Firefox a Edge s [TSUrlFilter][] v3.0 nebo novějším. Předchozí verze podporují pouze pravidla výjimek, která zakazují konkrétní skriptlety.
:::
### Důvěryhodné skriptlety {#trusted-scriptlets}
-Trusted scriptlets are [scriptlets](#scriptlets) with extended functionality. It means the same syntax and restrictions. Trusted scriptlet names are prefixed with `trusted-`, e.g. `trusted-set-cookie`, to be easily distinguished from common scriptlets.
+Důvěryhodné skriptlety jsou skriptlety [](#scriptlets) s rozšířenou funkčností. Znamená to stejnou syntaxi a omezení. Názvy důvěryhodných skriptletů mají předponu `trusted-`, např. `trusted-set-cookie`, aby je bylo možné snadno odlišit od běžných skriptletů.
:::note
-Trusted scriptlets are not compatible with other ad blockers except AdGuard.
+Důvěryhodné skriptlety nejsou kompatibilní s jinými blokátory reklam kromě AdGuardu.
:::
:::caution Omezení
-Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters).
+Důvěryhodné skriplety lze použít pouze [**v důvěryhodných filtrech**](#trusted-filters).
:::
:::info Kompatibilita
-Trusted scriptlets rules are not supported by AdGuard Content Blocker.
+Důvěryhodné skriplety nejsou Blokátorem obsahu AdGuard podporovány.
:::
-Learn more about [how to debug scriptlets](#debug-scriptlets).
+Další informace o [ladění skriptletů](#debug-scriptlets).
-More information about trusted scriptlets can be found [on GitHub](https://github.com/AdguardTeam/Scriptlets#trusted-scriptlets).
+Další informace o důvěryhodných skriptletech najdete na [GitHubu](https://github.com/AdguardTeam/Scriptlets#trusted-scriptlets).
## Modifikátory pro ostatní typ pravidel {#non-basic-rules-modifiers}
-Each rule can be modified using the modifiers described in the following paragraphs.
+Každé pravidlo lze upravit pomocí modifikátorů popsaných v následujících odstavcích.
-**Syntax** {#non-basic-rules-modifiers-syntax}
+**Syntaxe** {#non-basic-rules-modifiers-syntax}
```text
rule = "[$" modifiers "]" [rule text]
@@ -4452,9 +4484,9 @@ modifiers = modifier0[, modifier1[, ...[, modifierN]]]
- **`modifier`** — sada modifikátorů popsaných níže.
- **`rule text`** — pravidlo, které je třeba změnit.
-For example, `[$domain=example.com,app=test_app]##selector`.
+Např.: `[$domain=example.com,app=test_app]##selector`.
-In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`.
+V modifikátorech musí být uvozeny hodnoty následujících znaků: `[`, `]`, `,`a `\` (pokud se pro uvození nepoužívá). K uvození použijte `\`. Např. uvozená závorka vypadá takto: `\]`.
| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] |
| ------------------------------------- |:----------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:|
@@ -4473,7 +4505,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,`
### **`$app`** {#non-basic-app-modifier}
-`$app` modifier lets you narrow the rule coverage down to a specific application or a list of applications. The modifier's behavior and syntax perfectly match the corresponding [basic rules `$app` modifier](#app-modifier).
+Modifikátor `$app` umožňuje zúžit pokrytí pravidla na konkrétní aplikaci, nebo seznam aplikací. Chování a syntaxe modifikátoru dokonale odpovídají příslušným [základním pravidlům modifikátoru `$app`](#app-modifier).
**Příklady**
@@ -4484,13 +4516,13 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,`
:::info Kompatibilita
-Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux.
+Taková pravidla s modifikátorem `$app` podporuje AdGuard pro Windows, Mac, Android a Linux.
:::
### **`$domain`** {#non-basic-domain-modifier}
-`$domain` modifier limits the rule application area to a list of domains and their subdomains. The modifier's behavior and syntax perfectly match the corresponding [basic rules `$domain` modifier](#domain-modifier).
+Modifikátor `$domain` omezuje oblast použití pravidla na seznam domén a jejich subdomén. Chování a syntaxe modifikátoru dokonale odpovídají příslušným [základním pravidlům modifikátoru `$domain`](#domain-modifier).
**Příklady**
@@ -4498,30 +4530,30 @@ Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard fo
- `[$domain=example.com|example.org]###adblock` — skryje prvek s atributem `id`, který se rovná `adblock` na `example.com`, `example.org` a všech subdoménách.
- `[$domain=~example.com]##.textad` — toto pravidlo skryje prvek `div` se třídou `textad` na všech doménách kromě `example.com` a jejích subdomén.
-There are 2 ways to specify domain restrictions for non-basic rules:
+Existují 2 způsoby, jak určit omezení domény pro ostatní pravidla:
-1. the "classic" way is to specify domains before rule mask and attributes: `example.com##.textad`;
-2. the modifier approach is to specify domains via `$domain` modifier: `[$domain=example.com]##.textad`.
+1. "klasický" způsob je zadat domény před masku pravidla a atributy: `example.com##.textad`;
+2. přístup modifikátoru spočívá v určení domén pomocí modifikátoru `$domain`: `[$domain=example.com]##.textad`.
-But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored.
+Pravidla s omezením domén smíšeného stylu jsou však považována za neplatná. Takže např. pravidlo `[$domain=example.org]example.com##.textad` bude zamítnuto.
### Nezákladní omezení modifikátoru `$domain` {#non-basic-domain-modifier-limitations}
:::caution Omezení
-Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations).
+Vzhledem k tomu, že nezákladní modifikátor `$domain` funguje stejně jako základní, má stejná [omezení](#domain-modifier-limitations).
:::
:::info Kompatibilita
-Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, Chrome MV3, Firefox, and Edge.
+Pravidla s modifikátorem `$domain` podporuje AdGuard pro Windows, AdGuard pro macOS, AdGuard pro Android, Rozšíření prohlížeče AdGuard pro Chrome, Chrome MV3, Firefox a Edge.
:::
### **`$path`** {#non-basic-path-modifier}
-`$path` modifier limits the rule application area to specific locations or pages on websites.
+Modifikátor `$path` omezuje oblast použití pravidel na konkrétní umístění nebo stránky na webových stránkách.
**Syntaxe**
@@ -4529,13 +4561,13 @@ Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard
$path ["=" pattern]
```
-`pattern` — optional, a path mask to which the rule is restricted. Its syntax and behavior are pretty much the same as with the [pattern for basic rules](#basic-rules-syntax). You can also use [special characters](#basic-rules-special-characters), except for `||`, which does not make any sense in this case (see examples below).
+`pattern` — volitelný, maska cesty, na kterou je pravidlo omezeno. Jeho syntaxe a chování jsou v podstatě stejné jako u [vzoru pro základní pravidla](#basic-rules-syntax). Můžete také použít [speciální znaky](#basic-rules-special-characters) s výjimkou `||`, což v tomto případě nemá smysl (viz příklady níže).
-If `pattern` is not set for `$path`, rule will apply only on the main page of website.
+Pokud není nastaven `pattern` pro `$path`, pravidlo bude platit pouze na hlavní stránce webu.
-`$path` modifier matches the query string as well.
+Modifikátor `$path` odpovídá i řetězci dotazu.
-`$path` modifier supports regular expressions in [the same way](#regexp-support) basic rules do.
+Modifikátor `$path` podporuje regulární výrazy [stejným způsobem](#regexp-support) jako základní pravidla.
**Příklady**
@@ -4550,13 +4582,13 @@ If `pattern` is not set for `$path`, rule will apply only on the main page of we
:::info Kompatibilita
-Rules with `$path` modifier are not supported by AdGuard Content Blocker.
+Pravidla s modifikátorem `$path` nejsou Blokátorem obsahu AdGuard podporována.
:::
### **`$url`** {#non-basic-url-modifier}
-`$url` modifier limits the rule application area to URLs matching the specified mask.
+Modifikátor `$url` omezuje oblast použití pravidla na adresy URL odpovídající zadané masce.
**Syntaxe**
@@ -4564,7 +4596,7 @@ Rules with `$path` modifier are not supported by AdGuard Content Blocker.
url = pattern
```
-where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic-rules-syntax) assuming that [some characters](#non-basic-rules-modifiers-syntax) must be escaped. The [special characters](#basic-rules-special-characters) and [regular expressions](#regexp-support) are supported as well.
+kde `pattern` je v podstatě stejný jako [`pattern` základních pravidel](#basic-rules-syntax) za předpokladu, že [některé znaky](#non-basic-rules-modifiers-syntax) musí být uvozeny. Podporovány jsou také [speciální znaky](#basic-rules-special-characters) a [regulární výrazy](#regexp-support).
**Příklady**
@@ -4576,23 +4608,23 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic
:::caution Omezení
-In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied.
+V rozšíření prohlížeče AdGuard, nezákladní `$url` modifikátor není kompatibilní s pravidly specifickými pro doménu a dalšími nezákladními modifikátory — [`$domain`](#non-basic-domain-modifier) a [`$path`](#non-basic-path-modifier). Např. pravidlo `[$url=/category/*]example.com###textad` nebude použito.
:::
:::info Kompatibilita
-Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later.
+Pravidla s modifikátorem `$url` jsou podporována AdGuardem pro Windows, AdGuardem pro Mac, AdGuardem pro Android a AdGuardem pro Linux s [CoreLibs][] v1.11 nebo novějším a rozšířením prohlížeče AdGuard s [TSUrlFilter][] v3.0.0 nebo novějším.
:::
## Informace pro správce filtrů
-If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters).
+Pokud spravujete filtr třetí strany, který je AdGuardu znám, mohly by vás zajímat informace uvedené v této části. Upozorňujeme, že nápovědy se použijí pouze na registrované filtry. Filtr je považován za registrovaný a známý pro AdGuard, pokud je přítomen v [indexu známých filtrů](https://filters.adtidy.org/extension/chromium/filters.json). Pokud chcete, aby byl váš filtr zaregistrován, odešlete žádost do [repozitáře AdguardFilters](https://github.com/AdguardTeam/AdguardFilters).
### Direktivy preprocesoru
-We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide:
+Poskytujeme preprocesorové direktivy, které mohou být použity správci filtrů pro zlepšení kompatibility s různými blokátory reklam a poskytujeme:
- [zahrnutý soubor](#include-directive)
- [použití pravidel podmíněně podle typu blokátoru reklam](#conditions-directive)
@@ -4600,15 +4632,15 @@ We provide preprocessor directives that can be used by filter maintainers to imp
:::note
-Any mistake in a preprocessor directive will lead to AdGuard failing the filter update in the same way as if the filter URL was unavailable.
+Jakákoli chyba v direktivě preprocesoru povede k tomu, že AdGuard selže při aktualizaci filtru stejným způsobem, jako kdyby adresa URL filtru byla nedostupná.
-Preprocessor directives can be used in the user rules or in the custom filters.
+Direktivy preprocesoru lze použít v uživatelských pravidlech nebo ve vlastních filtrech.
:::
#### Zahrnutý soubor {#include-directive}
-The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism.
+Direktiva `!#include` umožňuje zahrnout do filtru obsah zadaného souboru. Podporuje pouze soubory ze stejného původu, aby bylo zajištěno, že správce filtru má kontrolu nad zadaným souborem. Zahrnutý soubor může také obsahovat pre-direktivy (i další `!#include` direktivy). Blokátory reklam by měly zvážit případ rekurzivního `!#include` a implementovat ochranný mechanismus.
**Syntaxe**
@@ -4616,17 +4648,17 @@ The `!#include` directive allows to include contents of a specified file into th
!#include file_path
```
-where `file_path` is a same origin absolute or relative file path to be included.
+kde `file_path` je absolutní nebo relativní cesta k souboru stejného původu, který má být zahrnut.
-The files must originate from the same domain, but may be located in a different folder.
+Soubory musí pocházet ze stejné domény, ale mohou být umístěny v jiné složce.
-If included file is not found or unavailable, the whole filter update should fail.
+Pokud obsažený soubor není nalezen nebo není k dispozici, celá aktualizace filtru by měla selhat.
-Same-origin limitation should be disabled for local custom filters.
+Omezení stejného původu by mělo být pro místní vlastní filtry zakázáno.
**Příklady**
-Filter URL: `https://example.org/path/filter.txt`
+URL filtru: `https://example.org/path/filter.txt`
```adblock
! Valid (same origin):
@@ -4642,17 +4674,17 @@ Filter URL: `https://example.org/path/filter.txt`
#### Podmínky {#conditions-directive}
-Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators.
+Správci filtrů mohou pomocí podmínek zadávat různá pravidla v závislosti na typu blokátoru reklam. Podmíněná direktiva začínající direktivou `!#if` musí být explicitně ukončena direktivou `!#endif`. Podmínky podporují všechny základní logické operátory.
-There are two possible scenarios:
+Existují dva možné scénáře:
-1. When an ad blocker encounters an `!#if` directive and no `!#else` directive, it will compile the code between `!#if` and `!#endif` directives only if the specified condition is true.
+1. Pokud blokátor reklamy narazí na direktivu `!#if` a ne `!#else`, zkompiluje kód mezi direktivami `!#if` a `!#endif` pouze v případě, že je zadaná podmínka pravdivá.
-1. If there is an `!#else` directive, the code between `!#if` and `!#else` will be compiled if the condition is true; otherwise, the code between `!#else` and `!#endif` will be compiled.
+1. Pokud existuje direktiva `!#else`, bude zkompilován kód mezi `!#if` a `!#else`, pokud je podmínka pravdivá; v opačném případě bude zkompilován kód mezi `!#else` a `!#endif`.
:::note
-Whitespaces matter. `!#if` is a valid directive, while `!# if` is not.
+Na mezerách záleží. `!#if` je platná direktiva, zatímco `!# if` není.
:::
@@ -4701,7 +4733,7 @@ kde:
**Příklady**
```adblock
-! for all AdGuard products except AdGuard for Safari
+! pro všechny produkty AdGuardu kromě AdGuardu pro Safari
!#if (adguard && !adguard_ext_safari)
||example.org^$third-party
domain.com##div.ad
@@ -4709,7 +4741,7 @@ domain.com##div.ad
```
```adblock
-! directives even can be combined
+! direktivy lze dokonce kombinovat
!#if (adguard_app_android)
!#include /androidspecific.txt
!#endif
@@ -4717,20 +4749,20 @@ domain.com##div.ad
```adblock
!#if (adguard && !adguard_ext_safari)
-! for all AdGuard products except AdGuard for Safari
+! pro všechny produkty AdGuardu kromě AdGuardu pro Safari
||example.org^$third-party
domain.com##div.ad
!#else
-! for AdGuard for Safari only
-||subdomain.example.org^$third-party
+! pouze pro AdGuard pro Safari
+||subdomena.example.org^$third-party
!#endif
```
:::info Kompatibilita
-The `!#else` directive is supported by the [FiltersDownloader][gh-filters-downloader] v1.1.20 or later.
+Direktivu `!#else` podporuje [FiltersDownloader][gh-filters-downloader] v1.1.20 nebo novější.
-It is already supported for filter lists compiled by the [FiltersRegistry][], but it still may not be supported by AdGuard products when adding a filter list with `!#else` as a custom one. The following products will support it in the mentioned versions or later:
+Je již podporována pro seznamy filtrů sestavené pomocí [FiltersRegistry][], ale stále nemusí být podporována produkty AdGuardu při přidání seznamu filtrů s `!#else` jako vlastních. Následující produkty ji budou podporovat ve zmíněných nebo novějších verzích:
- AdGuard pro Windows, Mac a Android s [CoreLibs][] v1.13;
- Rozšíření prohlížeče AdGuard v4.2.208;
@@ -4740,9 +4772,9 @@ It is already supported for filter lists compiled by the [FiltersRegistry][], bu
#### Afinita Safari {#safari-affinity-directive}
-Safari's limit for each content blocker is 150,000 active rules. But in AdGuard for Safari and AdGuard for iOS, we've split the rules into 6 content blockers, thus increasing the rule limit to 900,000.
+Limit Safari pro každý blokátor obsahu je 150000 aktivních pravidel. V aplikacích AdGuard pro Safari a AdGuard pro iOS jsme však pravidla rozdělili do 6 blokátorů obsahu, čímž jsme zvýšili limit pravidel na 900000.
-Here is the composition of each content blocker:
+Zde je složení jednotlivých blokátorů obsahu:
- AdGuard General — Blokování reklam, jazykově specifické filtry
- AdGuard Privacy — Soukromí
@@ -4751,11 +4783,11 @@ Here is the composition of each content blocker:
- AdGuard Other — Jiné
- AdGuard Custom — Vlastní
-User rules and allowlist are added to every content blocker.
+Uživatelská pravidla a Seznam povolených jsou přidány do každého blokátoru obsahu.
:::caution
-The main disadvantage of using multiple content blockers is that rules from different blockers are applied independently. Blocking rules are not affected by this, but unblocking rules may cause problems. If a blocking rule is in one content blocker and an exception is in another, the exception will not work. Filter maintainers use `!#safari_cb_affinity` to define Safari content blocker affinity for the rules inside of the directive block.
+Hlavní nevýhodou používání více blokátorů obsahu je, že pravidla různých blokátorů se uplatňují nezávisle. Na pravidla blokování to nemá vliv, ale pro pravidla odblokování mohou způsobit problémy. Pokud je pravidlo blokování v jednom blokátoru obsahu a výjimka v jiném, výjimka nebude fungovat. Správci filtrů používají `!#safari_cb_affinity` k definování afinity blokátorů obsahu Safari pro pravidla uvnitř blokování direktiv.
:::
@@ -4784,14 +4816,14 @@ kde:
**Příklady**
```adblock
-! to unhide specific element which is hidden by AdGuard Base filter:
-!#safari_cb_affinity(general)
+! pro zobrazení konkrétního prvku, který je skryt základním filtrem AdGuardu:
+!#safari_cb_affinity(Obecné)
example.org#@#.adBanner
!#safari_cb_affinity
```
```adblock
-! to allowlist basic rule from AdGuard Tracking Protection filter:
+! pro seznam povolených základních pravidel z filtru AdGuard Tracking Protection:
!#safari_cb_affinity(privacy)
@@||example.org^
!#safari_cb_affinity
@@ -4799,7 +4831,7 @@ example.org#@#.adBanner
### Nápovědy
-"Hint" is a special comment, instruction to the filters compiler used on the server side (see [FiltersRegistry][]).
+"Hint" je speciální komentář, instrukce pro kompilátor filtrů používaný na straně serveru (viz [FiltersRegistry][]).
**Syntaxe**
@@ -4807,13 +4839,13 @@ example.org#@#.adBanner
!+ HINT_NAME1(PARAMS) HINT_NAME2(PARAMS)
```
-Multiple hints can be applied.
+Lze použít více nápověd.
#### Nápověda `NOT_OPTIMIZED`
-For each filter, AdGuard compiles two versions: full and optimized. Optimized version is much more lightweight and does not contain rules which are not used at all or used rarely.
+Pro každý filtr sestavuje AdGuard dvě verze: plnou a optimalizovanou. Optimalizovaná verze je mnohem jednodušší a neobsahuje pravidla, která se nepoužívají vůbec nebo jen zřídka.
-Rules usage frequency comes from the collected [filter rules statistics](../tracking-filter-statistics). But filters optimization is based on more than that — some filters have specific configuration. This is how it looks like for Base filter:
+Frekvence používání pravidel vychází ze shromážděných statistik [pravidel filtrování](../tracking-filter-statistics). Optimalizace filtrů je však založena na více než na tom — některé filtry mají specifickou konfiguraci. Takto to vypadá pro Základní filtr:
```text
"filter": AdGuard Base filter,
@@ -4831,21 +4863,21 @@ kde:
- **maxPercent** — horní mez hodnoty `percent` value
- **strict** — pokud je `percent < minPercent` NEBO `percent > maxPercent` a je zapnutý přísný režim, pak by kompilace filtru měla selhat, jinak je nutné použít původní pravidla
-In other words, `percent` is the "compression level". For instance, for the Base filter it is configured to 40%. It means that optimization algorithm should strip 60% of rules.
+Jinými slovy, `percent` je "úroveň komprese". Například pro Základní filtr je nastavena na 40 %. To znamená, že optimalizační algoritmus by měl odstranit 60 % pravidel.
-Eventually, here are the two versions of the Base filter for AdGuard Browser Extension:
+Nakonec zde jsou dvě verze základního filtru pro Rozšíření prohlížeče AdGuard:
- úplná: https://filters.adtidy.org/extension/chromium/filters/2.txt
- optimalizovaná: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt
-**If you want to add a rule which should not be removed at optimization use the `NOT_OPTIMIZED` hint:**
+**Pokud chcete přidat pravidlo, které by nemělo být při optimalizaci odstraněno, použijte nápovědu `NOT_OPTIMIZED`:**
```adblock
!+ NOT_OPTIMIZED
||example.org^
```
-**And this rule will not be optimized only for AdGuard for Android:**
+**Toto pravidlo nebude optimalizováno pouze pro AdGuard pro Android:**
```adblock
!+ NOT_OPTIMIZED PLATFORM(android)
@@ -4854,7 +4886,7 @@ Eventually, here are the two versions of the Base filter for AdGuard Browser Ext
#### Nápověda `PLATFORM` a `NOT_PLATFORM`
-Used to specify the platforms to apply the rules. List of existing platforms and links to Base filter, for example, for each of them:
+Slouží k zadání platforem pro použití pravidel. Seznam existujících platforem a odkazy např. na Základní filtr:
- `windows` — AdGuard pro Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt)
@@ -4884,14 +4916,14 @@ Used to specify the platforms to apply the rules. List of existing platforms and
**Příklady**
-This rule will be available only in AdGuard for Windows, Mac, Android:
+Toto pravidlo bude dostupné pouze v AdGuardu pro Windows, Mac a Android:
```adblock
!+ PLATFORM(windows,mac,android)
||example.org^
```
-Except for AdGuard for Safari, AdGuard Content Blocker, and AdGuard for iOS, this rule is available on all platforms:
+S výjimkou AdGuardu pro Safari, Blokátoru obsahu AdGuard a AdGuardu pro iOS je toto pravidlo k dispozici na všech platformách:
```adblock
!+ NOT_PLATFORM(ext_safari, ext_android_cb, ios)
@@ -4900,9 +4932,9 @@ Except for AdGuard for Safari, AdGuard Content Blocker, and AdGuard for iOS, thi
#### `NOT_VALIDATE`
-This hint is used to skip validation of the rule. It is useful for rules for which support has not yet been added to the filters compiler, or for rules that are incorrectly discarded.
+Tato nápověda slouží k přeskočení validace pravidla. Je to užitečné pro pravidla, pro která dosud nebyla do překladače filtrů přidána podpora, nebo pro pravidla, která jsou nesprávně vyřazena.
-**If you want to add a rule that should not be validated, use the `NOT_VALIDATE` hint:**
+**Pokud chcete přidat pravidlo, které by nemělo být validováno, použijte nápovědu `NOT_VALIDATE`:**
```adblock
!+ NOT_VALIDATE
@@ -4911,13 +4943,13 @@ This hint is used to skip validation of the rule. It is useful for rules for whi
## Jak ladit pravidla filtrování
-It may be possible to create simple filtering rules "in your head" but for anything even slightly more complicated you will need additional tools to debug and iterate them. There are tools to assist you with that. You can use DevTools in Chrome and its analogs in other browsers but most AdGuard products provide another one — Filtering log.
+Jednoduchá pravidla filtrování je možné vytvořit "v hlavě", ale pro cokoli alespoň trochu složitějšího budete potřebovat další nástroje pro jejich ladění a iteraci. Existují nástroje, které vám s tím pomohou. V prohlížeči Chrome a jeho analogiích v ostatních prohlížečích můžete použít nástroj DevTools, ale většina produktů AdGuardu nabízí ještě jeden — Záznam filtrování.
### Záznam filtrování
-Filtering log is an advanced tool that will be helpful mostly to filter developers. It lists all web requests that pass through AdGuard, gives you exhaustive information on each of them, offers multiple sorting options, and has other useful features.
+Záznam filtrování je pokročilý nástroj, který bude užitečný především pro vývojáře filtrů. Obsahuje seznam všech webových požadavků, které procházejí skrze AdGuard, poskytuje vyčerpávající informace o každém z nich, nabízí několik možností třídění a další užitečné funkce.
-Depending on which AdGuard product you are using, Filtering log can be located in different places.
+V závislosti na tom, který AdGuard produkt používáte, se protokol filtrování může nacházet na různých místech.
- V **AdGuardu pro Windows** jej najdete na kartě *Blokátor reklam* nebo prostřednictvím nabídky na hlavním panelu
- V **AdGuardu pro Mac** je pod *Nastavení → Pokročilé → Záznam filtrování*
@@ -4926,17 +4958,17 @@ Depending on which AdGuard product you are using, Filtering log can be located i
:::note
-In **AdGuard for iOS** and **AdGuard for Safari**, Filtering log does not exist because of the way content blockers are implemented in Safari. AdGuard does not see the web requests and therefore cannot display them.
+V **AdGuardu pro iOS** a **AdGuardu pro Safari** Záznam filtrování neexistuje kvůli způsobu, jakým jsou v Safari implementovány blokátory obsahu. AdGuard tyto webové požadavky nevidí, a proto je nemůže zobrazit.
:::
### Režim ladění selektorů {#selectors-debug-mode}
-Sometimes, you might need to check the performance of a given selector or a stylesheet. In order to do it without interacting with JavaScript directly, you can use a special `debug` style property. When `ExtendedCss` meets this property, it enables the debugging mode either for a single selector or for all selectors, depending on the `debug` value.
+Někdy můžete potřebovat zkontrolovat výkonnost daného selektoru nebo souboru stylů. Abyste to mohli provést bez přímé interakce s JavaScript, můžete použít speciální vlastnost stylu `debug`. Když `ExtendedCss` splňuje tuto vlastnost, povolí režim ladění buď pro jeden selektor, nebo pro všechny selektory v závislosti na hodnotě `debug`.
-Open the browser console while on a web page to see the timing statistics for selector(s) that were applied there. Debugging mode displays the following stats as object where each of the debugged selectors are keys, and value is an object with such properties:
+Otevřete konzolu prohlížeče na webové stránce a zobrazte statistiky časování pro selektor(y), které zde byly použity. Režim ladění zobrazí následující statistiky jako objekt, kde každý z laděných selektorů je klíč a hodnota je objekt s těmito vlastnostmi:
-**Always printed:**
+**Vždy vytištěno:**
- `selectorParsed` — text parsovaného selektoru se může lišit od vstupního textu
- `timings` — seznam uzlů DOM odpovídajících selektoru
@@ -4946,44 +4978,44 @@ Open the browser console while on a web page to see the timing statistics for se
- `standardDeviation` — standardní odchylka
- `timingsSum` — celkový čas potřebný k použití selektoru na stránce ve všech instancích
-**Printed only for remove pseudos:**
+**Vytištěno pouze pro odstranění pseudonymů:**
- `removed` — příznak signalizující, zda byly prvky odstraněny
-**Printed if elements are not removed:**
+**Vytištěno, pokud prvky nejsou odstraněny:**
- `matchedElements` — seznam uzlů DOM odpovídajících selektoru
- `styleApplied` — parsovaná deklarace stylu pravidla související se selektorem
**Příklady**
-**Debugging a single selector:**
+**Ladění jednoho selektoru:**
-When the value of the `debug` property is `true`, only information about this selector will be shown in the browser console.
+Pokud je hodnota vlastnosti `debug` `true`, zobrazí se v konzole prohlížeče pouze informace o tomto selektoru.
```adblock
#$?#.banner { display: none; debug: true; }
```
-**Enabling global debug:**
+**Povolení globálního ladění:**
-When the value of the `debug` property is `global`, the console will display information about all extended CSS selectors that have matches on the current page, for all the rules from any of the enabled filters.
+Pokud je hodnota vlastnosti `debug` `global`, konzola zobrazí informace o všech rozšířených selektorech CSS, které mají na aktuální stránce shodu pro všechna pravidla z libovolného povoleného filtru.
```adblock
#$?#.banner { display: none; debug: global; }
```
-**Testing extended selectors without AdGuard**
+**Testování rozšířených selektorů bez AdGuardu**
-ExtendedCss can be executed on any page without using any AdGuard product. In order to do that you should copy and execute the following code in a browser console:
+ExtendedCss lze spustit na libovolné stránce bez použití AdGuard produktu. Za tímto účelem byste měli zkopírovat a spustit následující kód v konzoli prohlížeče:
```js
!function(e,t,d){C=e.createElement(t),C.src=d,C.onload=function(){alert("ExtendedCss loaded successfully")},s=e.getElementsByTagName(t)[0],s?s.parentNode.insertBefore(C,s):(h=e.getElementsByTagName("head")[0],h.appendChild(C))}(document,"script","https://AdguardTeam.github.io/ExtendedCss/extended-css.min.js");
```
-Alternatively, install the [ExtendedCssDebugger userscript](https://github.com/AdguardTeam/Userscripts/blob/master/extendedCssDebugger/extended-css.debugger.user.js).
+Případně nainstalujte [uživatelský skript ExtendedCssDebugger](https://github.com/AdguardTeam/Userscripts/blob/master/extendedCssDebugger/extended-css.debugger.user.js).
-Now you can now use the `ExtendedCss` from global scope, and run its method [`query()`](https://github.com/AdguardTeam/ExtendedCss#extended-css-query) as `Document.querySelectorAll()`.
+Nyní můžete použít `ExtendedCss` z globálního rozsahu a spustit jeho metodu [`query()`](https://github.com/AdguardTeam/ExtendedCss#extended-css-query) jako `Document.querySelectorAll()`.
**Příklady**
@@ -4996,9 +5028,9 @@ ExtendedCss.query(selector);
### Ladění skriptletů {#debug-scriptlets}
-If you are using AdGuard Browser Extension and want to debug a [scriptlet](#scriptlets) or a [trusted scriptlet](#trusted-scriptlets) rule, you can get additional information by opening the Filtering log. In that case, scriptlets will switch to debug mode and there will be more information in the browser console.
+Pokud používáte Rozšíření prohlížeče AdGuard a chcete vyladit pravidlo [skriptlet](#scriptlets) nebo [důvěryhodný skriptlet](#trusted-scriptlets), můžete získat další informace otevřením protokolu filtrování. V takovém případě se skriptlety přepnou do režimu ladění a v konzoli prohlížeče se zobrazí více informací.
-The following scriptlets are especially developed for debug purposes:
+Následující skriptlety jsou speciálně vyvinuty zejména pro účely ladění:
- [`debug-current-inline-script`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#debug-current-inline-script)
- [`debug-on-property-read`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#debug-on-property-read)
@@ -5008,7 +5040,7 @@ The following scriptlets are especially developed for debug purposes:
- [`log-eval`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#log-eval)
- [`log`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#log)
-The following scriptlets also may be used for debug purposes:
+Následující skriptlety lze také použít pro účely ladění:
- [`json-prune`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#json-prune)
- [`prevent-fetch`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-fetch)
@@ -5024,13 +5056,13 @@ The following scriptlets also may be used for debug purposes:
### Zkratky produktů {#what-product}
-1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking), and [AdGuard for Linux](/adguard-for-linux)
-1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge and Opera
-1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version)
-1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox
-1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser)
-1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general)
-1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser
+1. `Aplikace CoreLibs` — [AdGuard pro Windows](/adguard-for-windows/features/home-screen), [AdGuard pro Mac](/adguard-for-mac/features/main), [AdGuard pro Android](/adguard-for-android/features/protection/ad-blocking) a [AdGuard pro Linux](/adguard-for-linux)
+1. `AdGuard pro Chromium` — [Rozšíření prohlížeče AdGuard](/adguard-browser-extension/availability) pro Chrome a další prohlížeče založené na Chromium, např. nový Microsoft Edge a Opera
+1. `Adguard pro Chrome MV3` — [Rozšíření prohlížeče AdGuard pro Chrome MV3](/adguard-browser-extension/mv3-version)
+1. `Adguard pro Firefox` — [Rozšíření prohlížeče AdGuard](/adguard-browser-extension/availability) pro Firefox
+1. `AdGuard pro iOS` — [AdGuard pro iOS](/adguard-for-ios/features/safari-protection) a AdGuard pro iOS Pro (pro mobilní prohlížeč Safari)
+1. `AdGuard pro Safari` — [AdGuard pro desktopový prohlížeč Safari](/adguard-for-safari/features/general)
+1. `Blokátor obsahu AdGuard` — [blokátor obsahu](/adguard-content-blocker/overview) pro mobilní prohlížeče Android: Samsung Internet a Yandex Browser
### Zkratky kompatibility {#what-compatibility}
@@ -5070,11 +5102,8 @@ The following scriptlets also may be used for debug purposes:
[ext-ff]: #what-product "AdGuard Browser Extension for Firefox"
[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS"
[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS"
-[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS"
[ext-saf]: #what-product "AdGuard pro Safari"
[ext-saf]: #what-product "AdGuard for Safari"
-[ext-saf]: #what-product "AdGuard for Safari"
-[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android"
[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android"
[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android"
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md
index ef13c342fb4..d19d573d001 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md
@@ -13,7 +13,7 @@ Možnost *Odesílat statistiky o použití filtrů reklam* je ve výchozím nast
Nejprve si definujme, co jsou to filtry reklam. Díky těmto filtrům AdGuard odstraňuje reklamy z webových stránek. Jsou sestavovány ručně na základě vašich stížností na reklamy na webových stránkách. Filtry reklam jsou základním prvkem AdGuardu – jejich kvalita určuje celkovou kvalitu blokování reklam AdGuardem.
-Má to však i svou nevýhodu. V průběhu let se objevuje stále více filtrů reklam. Čím více je filtrů reklam, tím více paměti AdGuard spotřebovává a tím zpomaluje vykreslování webových stránek. Zároveň některé filtry začnou dosluhovat a postupně se stávají nefunkční. Nemají využití, pouze spotřebovávají paměť a zpomalují program.
+Má to však i svou nevýhodu. V průběhu let se objevuje stále více filtrů reklam. Čím více je reklamních filtrů, tím více paměti AdGuard spotřebovává, a tím zpomaluje vykreslování webových stránek. Zároveň některé filtry vyprší a postupně se stanou zbytečnými, čímž spotřebovávají paměť a zpomalují program.
### Proč potřebujeme statistiky?
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md
index 6d833c7be8a..0dcbc9b3b83 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md
@@ -79,7 +79,7 @@ Tuto možnost nedoporučujeme povolovat, protože může vážně narušit prác
:::
-Zakazuje prohlížeči Google Chrome odesílat informace o verzi a modifikaci s požadavky na domény Google (včetně DoubleClick a Google Analytics).
+:::note
K dispozici v AdGuard pro Android, AdGuard pro Windows, AdGuard pro Mac a Rozšíření prohlížeče AdGuard (prohlížeče založené na MV2).
@@ -89,7 +89,7 @@ K dispozici v AdGuard pro Android, AdGuard pro Windows, AdGuard pro Mac a Rozš
Tato funkce odstraňuje hlavičky ETag a If-None-Match z požadavků a odpovědí, aby se zabránilo jejich sledování.
-Když prohlížeč osloví stránku, server jí přiřadí značku ETag. Tato značka ETag používá prohlížeč k ukládání obsahu stránky do mezipaměti. Při dalších požadavcích prohlížeč odešle ETag příslušnému serveru, čímž mu umožní zjistit identitu návštěvníka. Dokud jsou soubory webu uloženy v mezipaměti, je značka ETag odesílána pokaždé, když se váš prohlížeč obrátí na tento web. Pokud je na webu vložen obsah z jiného serveru (například obrázek nebo iframe), může tento server sledovat vaše aktivity bez vašeho vědomí.
+Když prohlížeč osloví stránku, server jí přiřadí značku ETag. Tato značka ETag používá prohlížeč k ukládání obsahu stránky do mezipaměti. Při dalších požadavcích odešle prohlížeč příslušnému serveru značku ETag, čímž umožní serveru zjistit identitu návštěvníka. Dokud jsou soubory webu uloženy v mezipaměti, je značka ETag odesílána pokaždé, když se váš prohlížeč obrátí na tento web. Pokud je na webu vložen obsah z jiného serveru (například obrázek nebo iframe), může tento server sledovat vaše aktivity bez vašeho vědomí.
Zakazuje prohlížeči Google Chrome odesílat informace o verzi a modifikaci s požadavky na domény Google (včetně DoubleClick a Google Analytics).
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 99542633fec..d0275810cb2 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
@@ -77,7 +77,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli configure
```
- 
+ 
The wizard will ask basic questions required for the initial setup.
@@ -87,7 +87,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli start
```
- 
+ 
8. You can check the protection status using:
@@ -101,7 +101,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli stop
```
- 
+ 
9. To check the current configuration, enter:
@@ -109,7 +109,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli config show
```
- 
+ 
The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md
index a3d09d8c49a..100c4346eff 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/adguard-browser-extension.md
@@ -9,7 +9,7 @@ In diesem Artikel geht es um die AdGuard Browsereweiterung, die nur Ihren Browse
:::
-## Funktionen
+## Features
Die wichtigsten Funktionen und Einstellungen der AdGuard Browsererweiterung
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md
index 61bd5942025..c5a9f57f895 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/features.md
@@ -1,5 +1,5 @@
---
-title: Funktionen
+title: Features
sidebar_position: 1
---
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/adguard-for-android.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/adguard-for-android.md
index 5ccb63b0962..26c092c83a5 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/adguard-for-android.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/adguard-for-android.md
@@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc
:::
-## Funktionen
+## Features
Die wichtigsten Funktionen und Einstellungen von AdGuard für Android
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/features.md
index c2ff7783ae6..9edeabee6ff 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/features.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/features.md
@@ -1,5 +1,5 @@
---
-title: Funktionen
+title: Features
sidebar_position: 1
---
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md
index 6d332b871dc..02437a30512 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/low-level-settings.md
@@ -140,9 +140,9 @@ If this setting is enabled, AdGuard will filter requests sent over HTTP/3 in add
**Limitations**:
-- Chrome-based browsers do not accept user certificates, so HTTP/3 filtering is not supported in them.
+- Chromebasierte Browser akzeptieren keine Benutzerzertifikate, daher wird HTTP/3-Filterung in ihnen nicht unterstützt.
- Firefox-based browsers behave similarly by default, but you can set the `network.http.http3.disable_when_third_party_roots_found` option in `about:config` to `false` to allow user certificates for HTTP/3.
-- Safari supports HTTP/3 filtering without additional configuration.
+- Safari unterstützt HTTP/3-Filterung ohne zusätzliche Konfiguration.
### Outbound-Proxy
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 56d68b3715b..67eab424c94 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-for-ios.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-for-ios.md
index 77e843f45dc..addceee9cfa 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-for-ios.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-for-ios.md
@@ -3,7 +3,7 @@ title: AdGuard für iOS
sidebar_position: 1
---
-## Funktionen
+## Features
Die wichtigsten Funktionen und Einstellungen von AdGuard für iOS
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md
index 17ddcd3ff6b..ab674a75af4 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/features.md
@@ -1,5 +1,5 @@
---
-title: Funktionen
+title: Features
sidebar_position: 1
---
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 027dde52cae..bdb6828c39d 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard für Linux erfordert eine [AdGuard-Lizenz](https://adguard.com/license.h
2. Wählen Sie dann die gewünschte Option:
- 
+ 
3. Sobald Sie eine Lizenz besitzen, folgen Sie dem angegebenen Link, um mit der Aktivierung fortzufahren:
- 
+ 
4. Nach der Aktivierung können Sie mit der Anwendung weiterarbeiten:
- 
+ 
5. Sie können Ihre Lizenz zurücksetzen, indem Sie Folgendes eingeben:
@@ -77,7 +77,7 @@ AdGuard für Linux erfordert eine [AdGuard-Lizenz](https://adguard.com/license.h
adguard-cli configure
```
- 
+ 
Der Assistent stellt grundlegende Fragen, die für die Ersteinrichtung erforderlich sind.
@@ -87,7 +87,7 @@ AdGuard für Linux erfordert eine [AdGuard-Lizenz](https://adguard.com/license.h
adguard-cli start
```
- 
+ 
8. Sie können den Schutzstatus überprüfen mit:
@@ -109,7 +109,7 @@ AdGuard für Linux erfordert eine [AdGuard-Lizenz](https://adguard.com/license.h
adguard-cli config show
```
- 
+ 
Dabei wird auch der Pfad zur Konfigurationsdatei angezeigt, die Sie direkt bearbeiten sollten. Sie enthält Beschreibungen aller zusätzlichen Optionen.
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md
index 352ad8fa3bd..c4add513c48 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/adguard-for-mac.md
@@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker,
:::
-## Funktionen
+## Features
Die wichtigsten Funktionen und Einstellungen von AdGuard für Mac
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md
index 2e3c05a82a0..fefb39f99d7 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/features/features.md
@@ -1,5 +1,5 @@
---
-title: Funktionen
+title: Features
sidebar_position: 1
---
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md
index d5bd8b1bc9a..8fe28cbdd8e 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md
@@ -81,11 +81,11 @@ Verwendet einen lokalen DNS-Proxy für die Suche nach Konfigurationen in den ECH
Mit der Einstellung `true` erlauben Sie AdGuard, Datenverkehr zu filtern, der über HTTP/3, die neueste Version des auf QUIC-basierenden HTTP-Protokolls, gesendet wird.
-**Limitations**:
+**Einschränkungen**:
-- Chrome-based browsers do not accept user certificates, so HTTP/3 filtering is not supported in them.
-- Firefox-based browsers behave similarly by default, but you can set the `network.http.http3.disable_when_third_party_roots_found` option in `about:config` to `false` to allow user certificates for HTTP/3.
-- Safari supports HTTP/3 filtering without additional configuration.
+- Chromebasierte Browser akzeptieren keine Benutzerzertifikate, daher wird HTTP/3-Filterung in ihnen nicht unterstützt.
+- Firefox-basierte Browser verhalten sich standardmäßig ähnlich, aber Sie können die Option `network.http.http3.disable_when_third_party_roots_found` in `about:config` auf `false` setzen, um Benutzerzertifikate für HTTP/3 zuzulassen.
+- Safari unterstützt HTTP/3-Filterung ohne zusätzliche Konfiguration.
#### `network.filtering.localnetwork`
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md
index 28624ada09a..ea9c0e97c55 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/features.md
@@ -1,5 +1,5 @@
---
-title: Funktionen
+title: Features
sidebar_position: 1
---
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md
index 0dfb0fb22f3..05367644977 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/adguard-for-windows.md
@@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc
:::
-## Funktionen
+## Features
Die wichtigsten Funktionen und Einstellungen von AdGuard für Windows
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md
index 4478cea1c3d..e0eb8552db1 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/features.md
@@ -1,5 +1,5 @@
---
-title: Funktionen
+title: Features
sidebar_position: 1
---
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md
index 445c908d870..aab2524751a 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md
@@ -11,15 +11,15 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc
_Einstellungen_ ist der Bereich, der die meiste Aufmerksamkeit erfordert. Hier können Sie die App so konfigurieren, dass sie genau Ihren Bedürfnissen entspricht: Sie blockiert nur das, was Sie stört, verwendet den DNS-Server des vertrauenswürdigen Anbieters, entfernt Cookies von Drittanbietern und so weiter.
-### General settings
+### Allgemeine Einstellungen
-Here you can set the language and theme (Dark or Light), enable AdGuard launching at system start-up and silent automatic updates, choose the update channel and filter update check interval. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md).
+Hier können Sie die Sprache und das Design (dunkel oder hell) festlegen, den Start von AdGuard beim Systemstart und automatische Aktualisierungen im Hintergrund aktivieren, den Aktualisierungskanal auswählen und die Häufigkeit der Filteraktualisierungen festlegen. Die Einstellungen sind auch der richtige Ort, wenn AdGuard für Windows nicht richtig funktioniert und das Support-Team Sie gebeten hat, _Fehlersuchprotokolle_ zu erfassen (/adguard-for-windows/solving-problems/adguard-logs.md).
-
+
-At the very bottom of the screen you will find _Advanced Settings_. Changing some of them mindlessly may potentially cause problems with AdGuard’s performance, break the Internet connection or compromise your security and privacy. That’s why we suggest you open this section only if you are sure of what you are doing or our support team has asked you about it. If you want to know what can be set up in _Advanced Settings_, read the [dedicated article](/adguard-for-windows/solving-problems/low-level-settings.md).
+Ganz unten auf dem Bildschirm finden Sie _Erweiterte Einstellungen_. Wenn Sie einige von ihnen unbedacht ändern, kann dies zu Problemen mit der Leistung führen, die Internetverbindung unterbrechen oder Ihre Sicherheit und Privatsphäre gefährden. Deshalb empfehlen wir Ihnen, diesen Bereich nur zu öffnen, wenn Sie sicher sind, was Sie tun, oder wenn unser Support-Team Sie danach gefragt hat. Wenn Sie wissen möchten, was unter _Erweiterte Einstellungen_ eingestellt werden kann, lesen Sie den [entsprechenden Artikel](/adguard-for-windows/solving-problems/low-level-settings.md).
-
+
### Werbeblocker
@@ -46,9 +46,9 @@ Viele Websites sammeln Informationen über Personen, die sie besuchen, z. B. ihr
-You can flexibly adjust the work of _Tracking protection_: for instance, you can prohibit the website to receive the search request you used to find it on the Internet, automatically delete both third-party and website’s own cookies, and disable location sharing in your browser that can be used to track your whereabouts.
+Sie können die Funktionsweise dieses Moduls flexibel anpassen: Sie können z. B. verhindern, dass die Website die Suchanfrage erhält, mit der Sie sie im Internet gefunden haben. Sie können Cookies von Drittanbietern und der Website selbst automatisch löschen und Sie können die Standortfreigabe in Ihrem Browser deaktivieren, die dazu verwendet werden kann, Ihren Aufenthaltsort zu verfolgen.
-To learn everything about _Tracking protection_ and its many options, [read this article](/general/stealth-mode).
+Um alles über das Modul Tracking-Schutz und seine Optionen zu erfahren, [lesen Sie diesen Artikel](/general/stealth-mode).
### Internetsicherheit
@@ -81,15 +81,15 @@ Ab Version 7.20 können Sie Filter auch hinzufügen, indem Sie sie einfach aus e
-### Parental control
+### Kindersicherung
-Es gibt eine Reihe von Websites, auf die der Zugriff von einem von Kindern benutzten PC aus beschränkt werden sollte. This task is accomplished by _Parental control_.
+Es gibt eine Reihe von Websites, auf die der Zugriff von einem von Kindern benutzten PC aus beschränkt werden sollte. Diese Aufgabe wird von der _Kindersicherung_ wahrgenommen.
-
+
-Das Modul prüft den Inhalt der im Browser geöffneten Webseiten und filtert diejenigen mit für Kinder unerwünschten Inhalten: Bilder und Texte für Erwachsene, Schimpfwörter, Gewalt, Drogenpropaganda usw. Parental control settings are password-protected so that the child is not able to go round the restrictions. Dieses Modul blockiert nicht nur die Weiterleitung auf unerwünschte Seiten, sondern kann auch die für Kinder ungeeigneten Links aus den Suchergebnissen entfernen.
+Das Modul prüft den Inhalt der im Browser geöffneten Webseiten und filtert diejenigen mit für Kinder unerwünschten Inhalten: Bilder und Texte für Erwachsene, Schimpfwörter, Gewalt, Drogenpropaganda usw. Die Einstellungen der Kindersicherung sind passwortgeschützt, so dass das Kind die Einschränkungen nicht umgehen kann. Dieses Modul blockiert nicht nur die Weiterleitung auf unerwünschte Seiten, sondern kann auch die für Kinder ungeeigneten Links aus den Suchergebnissen entfernen.
-In the _Parental control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Sie können auch das Kontrollkästchen _Herunterladen von ausführbaren Dateien sperren_ aktivieren, um zu verhindern, dass Ihr Kind Software auf den Computer herunterlädt und installiert. There are two more options in the _Parental control_ module: you can select a specific Windows user to be protected by _Parental control_ and set a password to protect AdGuard settings from change.
+Im Modul _Kindersicherung_ können Sie die _Sichere Suche_ aktivieren und die _Sperrliste_ und die _Positivliste_ verwalten, um die Funktionsweise dieser Option anzupassen. Sie können auch das Kontrollkästchen _Herunterladen von ausführbaren Dateien sperren_ aktivieren, um zu verhindern, dass Ihr Kind Software auf den Computer herunterlädt und installiert. Im Modul _Kindersicherung_ gibt es zwei weitere Optionen: Sie können einen bestimmten Windows-Benutzer auswählen, der durch die _Kindersicherung_ geschützt werden soll, und ein Passwort festlegen, um die Einstellungen vor Änderungen zu schützen.
### Browser-Assistent
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md
index 22c0ed66273..1772bf3a189 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md
@@ -65,11 +65,11 @@ Aktivieren Sie diese Funktion, wenn Sie möchten, dass AdGuard automatisch Filte
Ist diese Option aktiviert, filtert AdGuard zusätzlich zu den anderen Anfragetypen auch Anfragen, die über HTTP/3 gesendet werden.
-**Limitations**:
+**Einschränkungen**:
-- Chrome-based browsers do not accept user certificates, so HTTP/3 filtering is not supported in them.
-- Firefox-based browsers behave similarly by default, but you can set the `network.http.http3.disable_when_third_party_roots_found` option in `about:config` to `false` to allow user certificates for HTTP/3.
-- Safari supports HTTP/3 filtering without additional configuration.
+- Chromebasierte Browser akzeptieren keine Benutzerzertifikate, daher wird HTTP/3-Filterung in ihnen nicht unterstützt.
+- Firefox-basierte Browser verhalten sich standardmäßig ähnlich, aber Sie können die Option `network.http.http3.disable_when_third_party_roots_found` in `about:config` auf `false` setzen, um Benutzerzertifikate für HTTP/3 zuzulassen.
+- Safari unterstützt HTTP/3-Filterung ohne zusätzliche Konfiguration.
### Umleitungstreiber-Modus verwenden
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index e4fa699bcee..e7a05aeadce 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Beispiele**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — diese Regel gilt für alle Domains, außer `domain.com` und seinen Subdomains. Ein Beispiel für eine Drittanbieteranfrage: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — diese Regel wird ausschließlich auf `domain.com`angewendet. Beispiel für eine Anfrage, die nicht von Dritten stammt: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Kompatibilität
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. Um verschiedene Domains zu einer Regel hinzuzufügen, benutzen Sie `|` als Trennungszeichen.
@@ -2736,7 +2748,7 @@ This modifier completely changes the rule behavior. If it is applied, the rule w
You will need some knowledge of regular expressions to use `$replace` modifier.
-**Funktionen**
+**Features**
- `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.).
- `$replace` rules do not apply if the size of the original response is more than 10 MB.
@@ -2809,7 +2821,7 @@ Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for
The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression.
-**Funktionen**
+**Features**
- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception.
- `$urltransform` will not be applied if the original URL is blocked by other rules.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Erweiterte CSS-Selektoren {#extended-css-selectors}
- [Beschränkungen](#extended-css-limitations)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 4262390c849..c36540b38e4 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 72c728708c0..4ddd13cb728 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard para Linux requiere una [licencia de AdGuard](https://adguard.com/licens
2. Luego selecciona la opción deseada:
- 
+ 
3. Una vez que tengas una licencia, sigue el enlace proporcionado para continuar con la activación:
- 
+ 
4. Después de la activación, puedes continuar trabajando con el programa:
- 
+ 
5. También puedes reiniciar tu licencia ingresando:
@@ -77,7 +77,7 @@ AdGuard para Linux requiere una [licencia de AdGuard](https://adguard.com/licens
adguard-cli configure
```
- 
+ 
El asistente hará preguntas básicas necesarias para la configuración inicial.
@@ -87,7 +87,7 @@ AdGuard para Linux requiere una [licencia de AdGuard](https://adguard.com/licens
adguard-cli start
```
- 
+ 
8. Puedes verificar el estado de la protección usando:
@@ -101,7 +101,7 @@ AdGuard para Linux requiere una [licencia de AdGuard](https://adguard.com/licens
adguard-cli stop
```
- 
+ 
9. Para comprobar la configuración actual, ingresa:
@@ -109,7 +109,7 @@ AdGuard para Linux requiere una [licencia de AdGuard](https://adguard.com/licens
adguard-cli config show
```
- 
+ 
También se mostrará la ruta al archivo de configuración, que puedes y debes editar directamente. Contiene descripciones de todas las opciones adicionales.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 1966b3b7906..b4ef063563b 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`✅`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitaciones](#extended-css-limitations)
diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 18286d3ee23..5f80add41c8 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 95b82c745c3..12b0b68642f 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard pour Linux nécessite une [licence AdGuard](https://adguard.com/license.
2. Ensuite, sélectionnez l'option souhaitée :
- 
+ 
3. Dès que vous avez une licence, suivez le lien fourni pour procéder à l'activation :
- 
+ 
4. Après l'activation, vous pouvez continuer à travailler avec le programme :
- 
+ 
5. Vous pouvez également réinitialiser votre licence en saisissant :
@@ -77,7 +77,7 @@ AdGuard pour Linux nécessite une [licence AdGuard](https://adguard.com/license.
adguard-cli configure
```
- 
+ 
L'assistant posera des questions basiques obligatoires pour la configuration initiale.
@@ -87,7 +87,7 @@ AdGuard pour Linux nécessite une [licence AdGuard](https://adguard.com/license.
adguard-cli start
```
- 
+ 
8. Vous pouvez vérifier l'état de la protection en utilisant :
@@ -101,7 +101,7 @@ AdGuard pour Linux nécessite une [licence AdGuard](https://adguard.com/license.
adguard-cli stop
```
- 
+ 
9. Pour vérifier la configuration actuelle, tapez :
@@ -109,7 +109,7 @@ AdGuard pour Linux nécessite une [licence AdGuard](https://adguard.com/license.
adguard-cli config show
```
- 
+ 
Le chemin vers le fichier de configuration sera également affiché, c'est possible et même nécessaire de le modifier directement. Il contient des descriptions de toutes les options supplémentaires.
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index d689aff3a24..3f95fef95d8 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/license/transfer.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/license/transfer.md
index 954e1482a41..55c1f13971e 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/general/license/transfer.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/license/transfer.md
@@ -11,15 +11,15 @@ La clef de licence peut être activée sur un [nombre limité d'appareils](../wh
#### Méthode 1
-On the device that you want to unbind, open the AdGuard app and click *Reset license* or *Log out*.
+Sur l'appareil que vous souhaitez dissocier, ouvrez l'app AdGuard et cliquez sur *Réinitialiser la licence* ou *Se déconnecter*.
#### Méthode 2
-As an alternative, you can remove the device in your AdGuard account:
+Vous pouvez également supprimer l'appareil dans votre compte AdGuard :
-1. Log in to your [AdGuard account](https://adguardaccount.com/).
+1. Accédez à votre [compte AdGuard](https://adguardaccount.com/).
-1. Open *AdGuard Ad Blocker* tab.
+1. Ouvrez l'onglet *Bloqueur AdGuard* .
@@ -31,7 +31,7 @@ As an alternative, you can remove the device in your AdGuard account:
-After you have unbound the number of devices you need, you will be able log in on new devices. The license will become bound to them.
+Après avoir dissocié le nombre d'appareils dont vous avez besoin, vous pourrez vous identifier sur de nouveaux appareils. La licence leur sera alors liée.
## Comment transférer une licence vers un autre compte AdGuard{#transferaccount}
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 0402f0fa68b..475a4131ef4 100644
--- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index a85ffd8b3f8..4ec47d867e9 100644
--- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 938d5acdbc7..b0ff9c92338 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index e81844035c4..445707b3dd6 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard per Linux richiede una [licenza AdGuard](https://adguard.com/license.htm
2. Quindi seleziona l'opzione desiderata:
- 
+ 
3. Una volta ottenuta la licenza, segui il collegamento fornito per procedere con l'attivazione:
- 
+ 
4. Dopo l'attivazione, puoi continuare a lavorare con il programma:
- 
+ 
5. Puoi anche reimpostare la tua licenza inserendo:
@@ -77,7 +77,7 @@ AdGuard per Linux richiede una [licenza AdGuard](https://adguard.com/license.htm
adguard-cli configure
```
- 
+ 
La procedura guidata farà domande di base obbligatorie per l'approntamento iniziale.
@@ -87,7 +87,7 @@ AdGuard per Linux richiede una [licenza AdGuard](https://adguard.com/license.htm
adguard-cli start
```
- 
+ 
8. Puoi controllare lo stato della protezione usando:
@@ -101,7 +101,7 @@ AdGuard per Linux richiede una [licenza AdGuard](https://adguard.com/license.htm
adguard-cli stop
```
- 
+ 
9. Per controllare la configurazione corrente, inserire:
@@ -109,7 +109,7 @@ AdGuard per Linux richiede una [licenza AdGuard](https://adguard.com/license.htm
adguard-cli config show
```
- 
+ 
Il percorso del file di configurazione sarà altresì mostrato, e puoi − e dovresti − modificarlo direttamente. Contiene descrizioni di tutte le opzioni aggiuntive.
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index c73acbbfd57..ce786a67ac3 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitazioni](#extended-css-limitations)
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/license/transfer.md b/i18n/it/docusaurus-plugin-content-docs/current/general/license/transfer.md
index 5b4ecf9a71c..f7b3bc5e160 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/general/license/transfer.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/general/license/transfer.md
@@ -11,15 +11,15 @@ La chiave di licenza è attivabile su un [numero limitato di dispositivi](../wha
#### Metodo 1
-On the device that you want to unbind, open the AdGuard app and click *Reset license* or *Log out*.
+Nel dispositivo che vuoi scollegare, apri l'app AdGuard e clicca *Reimposta licenza* o *Disconnetti*.
#### Metodo 2
-As an alternative, you can remove the device in your AdGuard account:
+In alternativa, puoi rimuovere il dispositivo nel tuo profilo AdGuard:
-1. Log in to your [AdGuard account](https://adguardaccount.com/).
+1. Accedi al tuo [profilo AdGuard](https://adguardaccount.com/).
-1. Open *AdGuard Ad Blocker* tab.
+1. Apri la scheda *AdGuard Ad Blocker*.
@@ -31,7 +31,7 @@ As an alternative, you can remove the device in your AdGuard account:
-After you have unbound the number of devices you need, you will be able log in on new devices. The license will become bound to them.
+Dopo che hai slegato il numero di dispositivi necessari, potrai accedere da nuovi dispositivi. La licenza diventerà legata a loro.
## Come trasferire la licenza su un altro account AdGuard{#transferaccount}
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index b42b8c0257f..80986070055 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 2253ef598fa..c87d4d3e65f 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard for Linuxをご利用いただくには[AdGuardライセンス](https://
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
@@ -77,7 +77,7 @@ AdGuard for Linuxをご利用いただくには[AdGuardライセンス](https://
adguard-cli configure
```
- 
+ 
The wizard will ask basic questions required for the initial setup.
@@ -87,7 +87,7 @@ AdGuard for Linuxをご利用いただくには[AdGuardライセンス](https://
adguard-cli start
```
- 
+ 
8. 保護ステータスを表示するには、以下を入力します：
@@ -101,7 +101,7 @@ AdGuard for Linuxをご利用いただくには[AdGuardライセンス](https://
adguard-cli stop
```
- 
+ 
9. 現在の構成を確認するには、以下のように入力します：
@@ -109,7 +109,7 @@ AdGuard for Linuxをご利用いただくには[AdGuardライセンス](https://
adguard-cli config show
```
- 
+ 
構成ファイルへのパスも表示されます。これは直接編集可能で編集すべきです。 すべての追加オプションの説明が含まれています。
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 6f29f852590..782fababf8a 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index ee9da174dd0..3084d9b1593 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 158cb5cdd70..ee30f0e12a1 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ Linux용 AdGuard에는 [AdGuard 라이선스](https://adguard.com/license.html)
2. 그런 다음 원하는 옵션을 선택합니다.
- 
+ 
3. 링크를 클릭하여 라이선스를 활성화합니다.
- 
+ 
4. 활성화 후에는 프로그램을 계속 사용할 수 있습니다.
- 
+ 
5. 입력하여 라이선스를 초기화할 수도 있습니다.
@@ -77,7 +77,7 @@ Linux용 AdGuard에는 [AdGuard 라이선스](https://adguard.com/license.html)
adguard-cli configure
```
- 
+ 
마법사는 초기 설정에 필요한 기본적인 질문을 합니다.
@@ -87,7 +87,7 @@ Linux용 AdGuard에는 [AdGuard 라이선스](https://adguard.com/license.html)
adguard-cli start
```
- 
+ 
8. 다음을 사용하여 보호 상태를 확인할 수 있습니다.
@@ -101,7 +101,7 @@ Linux용 AdGuard에는 [AdGuard 라이선스](https://adguard.com/license.html)
adguard-cli stop
```
- 
+ 
9. 현재 구성을 확인하려면 다음을 입력합니다.
@@ -109,7 +109,7 @@ Linux용 AdGuard에는 [AdGuard 라이선스](https://adguard.com/license.html)
adguard-cli config show
```
- 
+ 
구성 파일의 경로도 표시되며, 직접 편집할 수 있습니다. 여기에는 모든 추가 옵션에 대한 설명이 포함되어 있습니다.
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 6b2c64f5632..1abfd4560f3 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [제한](#extended-css-limitations)
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 96caf14c303..960889e30e4 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 0d697e315f4..99ff1dcf43a 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ O AdGuard para Linux requer uma [licença do AdGuard](https://adguard.com/licens
2. Em seguida, selecione a opção desejada:
- 
+ 
3. Uma vez que você tenha uma licença, siga o link fornecido para prosseguir com a ativação:
- 
+ 
4. Após a ativação, você pode continuar a trabalhar com o programa:
- 
+ 
5. Você pode também redefinir sua licença inserindo:
@@ -77,7 +77,7 @@ O AdGuard para Linux requer uma [licença do AdGuard](https://adguard.com/licens
adguard-cli configure
```
- 
+ 
O assistente fará perguntas básicas obrigatórias para a configuração inicial.
@@ -87,7 +87,7 @@ O AdGuard para Linux requer uma [licença do AdGuard](https://adguard.com/licens
adguard-cli start
```
- 
+ 
8. Você pode verificar o status da proteção usando:
@@ -101,7 +101,7 @@ O AdGuard para Linux requer uma [licença do AdGuard](https://adguard.com/licens
adguard-cli stop
```
- 
+ 
9. Para verificar a configuração atual, digite:
@@ -109,7 +109,7 @@ O AdGuard para Linux requer uma [licença do AdGuard](https://adguard.com/licens
adguard-cli config show
```
- 
+ 
O caminho para o arquivo de configuração também será mostrado, que você pode e deve editar diretamente. Ele contém descrições de todas as opções adicionais.
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 569ac78c2ac..ba27b797b58 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. Um exemplo de uma solicitação de terceiros: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
Proíbe o Google Chrome de enviar sua versão e informações de modificação com solicitações para domínios do Google (incluindo Double Click e Google Analytics).
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. Para adicionar vários domínios a uma regra, use o caractere `|` como separador.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Seletores CSS Estendidos {#extended-css-selectors}
- [Limitações](#extended-css-limitations)
diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index a4c3a21e8fa..a3765eed92d 100644
--- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 4ccbd6e4987..7238bb535c2 100644
--- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 99542633fec..d0275810cb2 100644
--- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
@@ -77,7 +77,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli configure
```
- 
+ 
The wizard will ask basic questions required for the initial setup.
@@ -87,7 +87,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli start
```
- 
+ 
8. You can check the protection status using:
@@ -101,7 +101,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli stop
```
- 
+ 
9. To check the current configuration, enter:
@@ -109,7 +109,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli config show
```
- 
+ 
The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 78a98bef3f2..5c9df215407 100644
--- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Exemple**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domeniu.com^$third-party` — această regulă se aplică tuturor domeniilor, exceptând `domeniu.com` și subdomeniile sale. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitări](#extended-css-limitations)
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 539f3bd33c5..17241649262 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ Android на заводской прошивке, как правило, не к
- Найдите **AdGuard** и включите опцию **Постоянное VPN-соединение**
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Откройте **Настройки**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 8868d407077..79f2792d96f 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/inst
2. Затем выберите нужную опцию:
- 
+ 
3. Перейдите по ссылке, чтобы активировать лицензию:
- 
+ 
4. После активации вы можете продолжить пользоваться программой:
- 
+ 
5. Вы также можете сбросить лицензию, введя:
@@ -77,7 +77,7 @@ curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/inst
adguard-cli configure
```
- 
+ 
Мастер задаст основные вопросы, необходимые для первоначальной настройки.
@@ -87,7 +87,7 @@ curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/inst
adguard-cli start
```
- 
+ 
8. Вы можете проверить статус защиты, используя:
@@ -101,7 +101,7 @@ curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/inst
adguard-cli stop
```
- 
+ 
9. Чтобы просмотреть текущую конфигурацию, введите:
@@ -109,7 +109,7 @@ curl -fsSL https://raw.githubusercontent.com/AdguardTeam/AdGuardCLI/nightly/inst
adguard-cli config show
```
- 
+ 
Также будет показан путь к файлу конфигурации, который можно и нужно редактировать напрямую. В нём содержатся описания всех дополнительных опций.
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 738391d8631..0fd2f2457ec 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Примеры**
- domain.com$strict-first-party — это правило применяется только к `domain.com`. Например, запрос с домена `domain.com` к домену `http://domain.com/icon.ico` — это запрос первой стороны. Запрос от `sub.domain.com` к `http://domain.com/icon.ico` рассматривается как сторонний (в отличие от модификатора `$~third-party`).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — правило применяется на всех сайтах, кроме `domain.com` и его поддоменов. Пример стороннего запроса: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — это правило применяется исключительно к `domain.com`. Пример запроса, который не является сторонним: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Совместимость
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. Чтобы добавить несколько доменов в одно правило, используйте символ `|` в качестве разделителя.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Расширенные CSS-селекторы {#extended-css-selectors}
- [Ограничения](#extended-css-limitations)
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 1c1ddf8c172..6c585d428bb 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 1e7358e9c86..a3d30a5b957 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
@@ -77,7 +77,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli configure
```
- 
+ 
The wizard will ask basic questions required for the initial setup.
@@ -87,7 +87,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli start
```
- 
+ 
8. You can check the protection status using:
@@ -101,7 +101,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli stop
```
- 
+ 
9. To check the current configuration, enter:
@@ -109,7 +109,7 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
adguard-cli config show
```
- 
+ 
The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index 1be5d6a4454..f3d5b4e953d 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Örnekler**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Uyumluluk
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::bilgi Adblock Plus uyumluluğu
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index 28cb352117b..1d349f855bf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 7f38a3fa6ef..8a759e46e2d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -49,15 +49,15 @@ Linux 版 AdGuard 需要 [AdGuard 许可证](https://adguard.com/license.html)
2. 然后选择所需的选项：
- 
+ 
3. 获得许可证后，请按提供的链接继续激活：
- 
+ 
4. 激活后，您可以继续使用该程序：
- 
+ 
5. 您还可以输入以下命令来重置许可证：
@@ -77,7 +77,7 @@ Linux 版 AdGuard 需要 [AdGuard 许可证](https://adguard.com/license.html)
adguard-cli configure
```
- 
+ 
向导会询问初始设置所需的基本问题。
@@ -87,7 +87,7 @@ Linux 版 AdGuard 需要 [AdGuard 许可证](https://adguard.com/license.html)
adguard-cli start
```
- 
+ 
8. 要查看保护状态，请输入以下命令：
@@ -101,7 +101,7 @@ Linux 版 AdGuard 需要 [AdGuard 许可证](https://adguard.com/license.html)
adguard-cli stop
```
- 
+ 
9. 要查看当前配置，请键入：
@@ -109,7 +109,7 @@ Linux 版 AdGuard 需要 [AdGuard 许可证](https://adguard.com/license.html)
adguard-cli config show
```
- 
+ 
配置文件的路径也将被显示，您应该编辑它。 它包含所有附加选项的描述。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index ba6883d002c..e98c770d065 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [限制](#extended-css-limitations)
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
index abbdcaa2269..7a9c39baaa9 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md
@@ -591,3 +591,33 @@ On devices running Realme UI 4.0, there are three key configurations to ensure t
- Find **AdGuard** and enable the **Always-on VPN** option
+
+## Motorola
+
+On Motorola devices, there are four key configurations to ensure that AdGuard works properly in the background.
+
+1. Allow background usage:
+
+ - Go to **Settings → Apps** and find **AdGuard**
+ - Open **App battery usage**
+ - Enable **Allow background battery usage**
+ - Tap the option with the toggle
+ - Set battery usage to **Unrestricted**
+
+1. Remove background activity restrictions:
+
+ - Go to **Settings**
+ - Scroll down and tap **Apps & notifications**
+ - Find **AdGuard** and open **Advanced → Battery**
+ - Tap **Background restriction** or **Background limits**
+ - If it says **Background activity restricted**, tap it and then tap **Remove**
+
+1. Manage background apps:
+
+ - Go to **Settings**, then type **Managing background apps** in the search bar
+ - Find **AdGuard** and enable the toggle to allow the app to run in the background
+
+1. Disable Adaptive Battery:
+
+ - Go to **Settings → Battery**
+ - Turn off the **Adaptive Battery** option
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
index 67126401ab4..d0275810cb2 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-linux/installation.md
@@ -43,89 +43,89 @@ AdGuard for Linux requires an [AdGuard license](https://adguard.com/license.html
1. After installation, enter:
- ```sh
- adguard-cli activate
- ```
+ ```sh
+ adguard-cli activate
+ ```
2. Then select the desired option:
- 
+ 
3. Once you have a license, follow the provided link to proceed with the activation:
- 
+ 
4. After activation, you can continue to work with the program:
- 
+ 
5. You can also reset your license by entering:
- ```sh
- adguard-cli reset-license
- ```
+ ```sh
+ adguard-cli reset-license
+ ```
- or view the license info by entering
+ or view the license info by entering
- ```sh
- adguard-cli license
- ```
+ ```sh
+ adguard-cli license
+ ```
6. Now you need to set up AdGuard CLI. To run the configuration wizard, enter:
- ```sh
- adguard-cli configure
- ```
+ ```sh
+ adguard-cli configure
+ ```
- 
+ 
- The wizard will ask basic questions required for the initial setup.
+ The wizard will ask basic questions required for the initial setup.
7. After that, you can start the AdGuard protection by entering
- ```sh
- adguard-cli start
- ```
+ ```sh
+ adguard-cli start
+ ```
- 
+ 
8. You can check the protection status using:
- ```sh
- adguard-cli status
- ```
+ ```sh
+ adguard-cli status
+ ```
- and stop it with:
+ and stop it with:
- ```sh
- adguard-cli stop
- ```
+ ```sh
+ adguard-cli stop
+ ```
- 
+ 
9. To check the current configuration, enter:
- ```sh
- adguard-cli config show
- ```
+ ```sh
+ adguard-cli config show
+ ```
- 
+ 
- The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
+ The path to the configuration file will also be displayed, which you can and should edit directly. It contains descriptions of all additional options.
- As an alternative, you can use the commands:
+ As an alternative, you can use the commands:
- ```sh
- adguard-cli config get
- ```
+ ```sh
+ adguard-cli config get
+ ```
- or:
+ or:
- ```sh
- adguard-cli config set
- ```
+ ```sh
+ adguard-cli config set
+ ```
- They are primarily intended for scripting, though.
+ They are primarily intended for scripting, though.
For further information on the available commands, check out the section [Settings and protection management](https://adguard.com/kb/adguard-for-linux/settings/).
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
index f571dc8cdb6..6e206cea4f2 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md
@@ -726,6 +726,8 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker.
Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname.
+Requests without a referrer are also treated as first-party requests, and the rules with the `$strict-first-party` modifier are applied to such requests.
+
**Examples**
- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier).
@@ -740,6 +742,8 @@ You can use a shorter name (alias) instead of using the full modifier name: `$st
Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs][] v1.16 or later.
+Requests without a referrer are matched by rules with `$strict-first-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
:::
#### **`$strict-third-party`** {#strict-third-party-modifier}
@@ -779,13 +783,15 @@ To be considered as such, a third-party request should meet one of the following
**`$third-party`:**
-- `||domain.com^$third-party` — this rule applies to all domains, except `domain.com` and its subdomains. An example of a third-party request: `http://example.org/banner.jpg`.
+- `||domain.com^$third-party` — this rule applies to all domains except `domain.com` and its subdomains. The rule is never applied if there is no referrer. An example of a third-party request: `http://example.org/banner.jpg`.
-If there is a `$~third-party` modifier, the rule is only applied to the requests that are not from third parties. Which means, they have to be sent from the same domain.
+If there is a `$~third-party` modifier, the rule is only applied to requests that are not from third parties. Which means they have to be sent from the same domain or shouldn't have a referrer at all.
**`$~third-party`:**
-- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`.
+- `||domain.com$~third-party` — this rule applies only to `domain.com` and its subdomains. Example of a non third-party request: `http://sub.domain.com/icon.ico`.
+
+Requests without a referrer are also treated as non third-party requests and the rules with the `$~third-party` modifier are applied to such requests.
:::note
@@ -793,6 +799,12 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p
:::
+:::info Compatibility
+
+Requests without a referrer are matched by rules with `$~third-party` in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.18 or later.
+
+:::
+
#### **`$to`** {#to-modifier}
`$to` limits the rule scope to requests made **to** the specified domains and their subdomains. To add multiple domains to one rule, use the `|` character as a separator.
@@ -3328,6 +3340,26 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr
:::
+:::info Adblock Plus compatibility
+
+In AdGuard products that use **CoreLibs version 1.18 or later**, you can also use element hiding rules to inject a `remove: true` declaration:
+
+```adblock
+example.org##body { remove: true; }
+```
+
+This usage is discouraged in favor of using [CSS rules](#cosmetic-css-rules) and is only supported for compatibility with filter lists written for Adblock Plus.
+
+Element hiding exceptions (`#@#`) are matched by the selector part only, ignoring the declarations block part. For example, the above rule can be disabled by any of the following exception rules:
+
+```adblock
+example.org#@#body
+example.org#@#body { remove: true; }
+example.org#@#body{remove:true;}
+```
+
+:::
+
### Extended CSS selectors {#extended-css-selectors}
- [Limitations](#extended-css-limitations)