From bffd0e1a2464d35e70e01dec2b2d7fdd63427477 Mon Sep 17 00:00:00 2001 From: SW1FT Date: Fri, 27 Mar 2015 19:22:35 +0000 Subject: [PATCH] Updated Dynamic filtering: disabling cosmetic filtering for the current site (markdown) --- ...tering:-disabling-cosmetic-filtering-for-the-current-site.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dynamic-filtering:-disabling-cosmetic-filtering-for-the-current-site.md b/Dynamic-filtering:-disabling-cosmetic-filtering-for-the-current-site.md index e5a3145..c9b8525 100644 --- a/Dynamic-filtering:-disabling-cosmetic-filtering-for-the-current-site.md +++ b/Dynamic-filtering:-disabling-cosmetic-filtering-for-the-current-site.md @@ -2,7 +2,7 @@ *** -Someone asked me if it was possible to disable cosmetic filtering for the current site, without disabling µBlock, so as to keep the ability to block 3rd parties, to prevent them from injecting their ads, trackers, analytics, etc. +Someone asked me if it was possible to disable cosmetic filtering for the current site, without disabling uBlock, so as to keep the ability to block 3rd parties, to prevent them from injecting their ads, trackers, analytics, etc. This is actually possible using dynamic filtering: a simple local `allow` rule (green) for the current site: