From fe53f3f0f0e5fa78175263d142a468741e784419 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Wed, 14 Oct 2015 08:30:29 -0400 Subject: [PATCH] Updated Inline script tag filtering (markdown) --- Inline-script-tag-filtering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Inline-script-tag-filtering.md b/Inline-script-tag-filtering.md index 7d7e88d..6f6dc07 100644 --- a/Inline-script-tag-filtering.md +++ b/Inline-script-tag-filtering.md @@ -98,7 +98,7 @@ The _uBlock filters_ list, which is selected by default, already contains a coup #### Why is the new inline script tag filter a cosmetic one? -Because blocking inline script tags is conceptually closer to cosmetic filtering than network filtering: inline script tags are embedded in a web page, so if the web page is downloaded, the inline script tags are downloaded -- there is no way around this. +Because blocking inline script tags are conceptually closer to cosmetic filtering than network filtering: inline script tags are embedded in a web page, so if the web page is downloaded, the inline script tags are downloaded -- there is no way around this. Whatever can't be blocked using a network request filter can be taken care by a cosmetic filter, which is the removal of DOM elements from a web page. Hence inline script tag filtering is implemented using the cosmetic filter syntax -- the only difference is that when blocked, inline script tags are not removed from view (they are already invisible) but instead the execution of the javascript code inside the script tag is blocked.