From 219bcd790df441c46b635ea18ba2f010371dbfb3 Mon Sep 17 00:00:00 2001 From: Hugo Xu Date: Wed, 2 May 2018 19:13:56 -0600 Subject: [PATCH] Update predefined whitelist to match recent changes --- Dashboard:-Whitelist.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Dashboard:-Whitelist.md b/Dashboard:-Whitelist.md index 93fdce1..edd238e 100644 --- a/Dashboard:-Whitelist.md +++ b/Dashboard:-Whitelist.md @@ -18,16 +18,18 @@ The _Whitelist_ pane allows you to review or edit the exisiting whitelist direct There are predefined whitelist directives when you first install uBO: about-scheme - behind-the-scene chrome-extension-scheme chrome-scheme moz-extension-scheme opera-scheme vivaldi-scheme + wyciwyg-scheme + +For Firefox Legacy platform, `behind-the-scene` is also in this predefined whitelist. You should not remove these predefined whitelist directives, unless you know _exactly_ the consequences of doing so. -Removing the predefined whitelist directives without understanding the consequences could cause your browser to malfunction. **This is especially true for the `behind-the-scene` whitelist directive.** +Removing the predefined whitelist directives without understanding the consequences could cause your browser to malfunction. **This is especially true for the `behind-the-scene` whitelist directive on Firefox Legacy platform.** If despite this warning you still want to remove one or more of the predefined whitelist directives, I strongly suggest to comment out an entry rather than outright delete it. To comment out an entry, just prefix it with `# `. This way you do not have to remember which predefined whitelist directive you removed, it will be just a matter of removing the `# ` prefix if ever you want to restore an entry.