From 7bf9c0a64c8b58163e57fffff716d0acbd35a28c Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 26 Nov 2017 09:47:54 -0500 Subject: [PATCH] Updated How to work only with global rules and all scripts blocked by default (markdown) --- ...only-with-global-rules-and-all-scripts-blocked-by-default.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md b/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md index 4074b36..7c75449 100644 --- a/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md +++ b/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md @@ -38,4 +38,6 @@ Now persist these changes by clicking the padlock icon (which should report that ![a](https://user-images.githubusercontent.com/585534/33241002-c12b7ffe-d28d-11e7-9af3-b9e78891aa70.png) +This is it. +Scripts and frames are not blocked everywhere, and simply creating an allow rule directly on whatever domain will enable scripts and frames to be loaded for that domain. If you persist such rule by clicking on the padlock, they become permanently part of your ruleset. \ No newline at end of file