From 76e7650425e206457033e380de25526c6bd83765 Mon Sep 17 00:00:00 2001 From: Maxim Topciu Date: Tue, 14 Apr 2026 15:18:12 +0300 Subject: [PATCH 1/2] Add caution notes about WebRTC blocking in browser extension documentation --- docs/adguard-browser-extension/features/stealth-mode.md | 6 ++++++ docs/general/ad-filtering/create-own-filters.md | 1 + docs/general/stealth-mode.md | 6 ++++++ 3 files changed, 13 insertions(+) diff --git a/docs/adguard-browser-extension/features/stealth-mode.md b/docs/adguard-browser-extension/features/stealth-mode.md index 3479f76f521..8c24ddb9e07 100644 --- a/docs/adguard-browser-extension/features/stealth-mode.md +++ b/docs/adguard-browser-extension/features/stealth-mode.md @@ -26,3 +26,9 @@ The purpose of *Tracking protection* is to safeguard your sensitive personal dat Browser extensions are limited to a specific browser and are subject to its technical restrictions. Therefore, they cannot offer all the tracking protection features available in full-fledged ad-blocking apps. ::: + +:::caution + +In AdGuard Browser Extension, the *Block WebRTC* option works globally — it either blocks or allows WebRTC for all websites. It cannot be controlled on a per-site basis. Exception rules like `@@||example.com^$stealth=webrtc` have no effect in the browser extension because the `webrtc` option is not among the [supported `$stealth` modifier options](/general/ad-filtering/create-own-filters#stealth-modifier). If you need per-site WebRTC control, use a full AdGuard app (for Windows, Mac, or Android). + +::: diff --git a/docs/general/ad-filtering/create-own-filters.md b/docs/general/ad-filtering/create-own-filters.md index 28cb3636f38..7ffcfb2ed53 100644 --- a/docs/general/ad-filtering/create-own-filters.md +++ b/docs/general/ad-filtering/create-own-filters.md @@ -1284,6 +1284,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with [CoreLibs] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter] v3.0.0 or later. +- In AdGuard Browser Extension, *Block WebRTC* is applied globally and cannot be controlled on a per-site basis. Exception rules like `$stealth=webrtc` have no effect. ::: diff --git a/docs/general/stealth-mode.md b/docs/general/stealth-mode.md index aa3a3f77f12..b10cc2fcbde 100644 --- a/docs/general/stealth-mode.md +++ b/docs/general/stealth-mode.md @@ -129,6 +129,12 @@ Enabling this option can disrupt the work of certain browser applications, such ::: +:::note + +In AdGuard Browser Extension, *Block WebRTC* is applied globally and cannot be controlled on a per-site basis. Exception rules like `@@||example.com^$stealth=webrtc` are not supported. For per-site WebRTC control, use a full AdGuard app (for Windows, Mac, or Android). + +::: + ### Block Push API {#push} This feature blocks push notifications from websites. From 4da32882792710ff66c49d8bf23dc8d5ac4be2cd Mon Sep 17 00:00:00 2001 From: Maxim Topciu Date: Wed, 15 Apr 2026 11:22:14 +0300 Subject: [PATCH 2/2] Refine wording for clarity on WebRTC blocking in browser extension documentation --- docs/adguard-browser-extension/features/stealth-mode.md | 2 +- docs/general/stealth-mode.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/adguard-browser-extension/features/stealth-mode.md b/docs/adguard-browser-extension/features/stealth-mode.md index 8c24ddb9e07..cf53c8cb836 100644 --- a/docs/adguard-browser-extension/features/stealth-mode.md +++ b/docs/adguard-browser-extension/features/stealth-mode.md @@ -29,6 +29,6 @@ Browser extensions are limited to a specific browser and are subject to its tech :::caution -In AdGuard Browser Extension, the *Block WebRTC* option works globally — it either blocks or allows WebRTC for all websites. It cannot be controlled on a per-site basis. Exception rules like `@@||example.com^$stealth=webrtc` have no effect in the browser extension because the `webrtc` option is not among the [supported `$stealth` modifier options](/general/ad-filtering/create-own-filters#stealth-modifier). If you need per-site WebRTC control, use a full AdGuard app (for Windows, Mac, or Android). +In AdGuard Browser Extension, the *Block WebRTC* option works globally — it either blocks or allows WebRTC for all websites. It cannot be controlled on a per-site basis. Exception rules like `@@||example.com^$stealth=webrtc` have no effect in the browser extension because the `webrtc` option is not among the [supported `$stealth` modifier options](/general/ad-filtering/create-own-filters#stealth-modifier). If you need per-site WebRTC control, use the full-fledged AdGuard app for Windows, Mac, or Android. ::: diff --git a/docs/general/stealth-mode.md b/docs/general/stealth-mode.md index b10cc2fcbde..702bdd3e02e 100644 --- a/docs/general/stealth-mode.md +++ b/docs/general/stealth-mode.md @@ -131,7 +131,7 @@ Enabling this option can disrupt the work of certain browser applications, such :::note -In AdGuard Browser Extension, *Block WebRTC* is applied globally and cannot be controlled on a per-site basis. Exception rules like `@@||example.com^$stealth=webrtc` are not supported. For per-site WebRTC control, use a full AdGuard app (for Windows, Mac, or Android). +In AdGuard Browser Extension, *Block WebRTC* is applied globally and cannot be controlled on a per-site basis. Exception rules like `@@||example.com^$stealth=webrtc` are not supported. For per-site WebRTC control, use the full-fledged AdGuard app for Windows, Mac, or Android. :::