1
0
mirror of https://github.com/gorhill/uBlock.git synced 2024-09-29 06:07:11 +02:00

Updated About the required permissions (markdown)

Patrick Pfister 2015-06-03 09:23:35 +02:00
parent d415468311
commit 788ac8864d

@ -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). "[`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: This is Privacy Badger required permissions:
"permissions": [ "permissions": [
@ -33,8 +35,6 @@ This is Privacy Badger required permissions:
"https://*/*" "https://*/*"
], ],
It should come as no surprise that privacy-minded extensions require the `privacy` permission.
### "Access your data on all web sites" ### "Access your data on all web sites"
Since [first version](https://github.com/gorhill/uBlock/blob/b5fdac90539b19a0db8f36ea537bd150edb4d9c8/manifest.json). Since [first version](https://github.com/gorhill/uBlock/blob/b5fdac90539b19a0db8f36ea537bd150edb4d9c8/manifest.json).