From 788ac8864d75545ad805edd94527d31776acef3f Mon Sep 17 00:00:00 2001 From: Patrick Pfister Date: Wed, 3 Jun 2015 09:23:35 +0200 Subject: [PATCH] Updated About the required permissions (markdown) --- About-the-required-permissions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/About-the-required-permissions.md b/About-the-required-permissions.md index 78048eb..1a9369f 100644 --- a/About-the-required-permissions.md +++ b/About-the-required-permissions.md @@ -17,6 +17,8 @@ uBlock's required permissions are the same as those of [Privacy Badger](https:// "[`privacy`](https://developer.chrome.com/extensions/privacy)" is the only permission added in [version 0.9.8.2](https://github.com/gorhill/uBlock/releases/tag/0.9.8.2). All the others were there since when uBlock was first published (except for `"contextMenus"` which was added at some point, to support blocking element from within the context menu). +The `privacy` permission is needed for uBlock to be able to disable the setting "Prefetch resources to load pages more quickly". This will ensure no connection is opened at all for blocked requests: It's for your own protection privacy-wise. + This is Privacy Badger required permissions: "permissions": [ @@ -33,8 +35,6 @@ This is Privacy Badger required permissions: "https://*/*" ], -It should come as no surprise that privacy-minded extensions require the `privacy` permission. - ### "Access your data on all web sites" Since [first version](https://github.com/gorhill/uBlock/blob/b5fdac90539b19a0db8f36ea537bd150edb4d9c8/manifest.json).