"permissions": [ "*://developer.mozilla.org/*", "webRequest" ]
permissions key to request special powers for your extension. This key is an array of strings, and each string is a request for a permission.
If you request permissions using this key, then the browser may inform the user at install time that the extension is requesting certain privileges, and ask them to confirm that they are happy to grant these privileges. The browser may also allow the user to inspect an extension's privileges after installation.
The key can contain three kinds of permissions:
- host permissions
- API permissions
- the activeTab permission
Host permissions are specified as match patterns, and each pattern identifies a group of URLs for which the extension is requesting extra privileges. For example, a host permission could be
The extra privileges include:
- XMLHttpRequest and fetch access to those origins without cross-origin restrictions (even for requests made from content scripts)
- the ability to inject scripts programmatically (using tabs.executeScript) into pages served from those origins
- the ability to receive events from the webRequest API for these hosts
- the ability to access cookies for that host using the cookies API, as long as the "cookies" API permission is also included.
- bypass tracking protection if the host is a full domain without wildcards. Doesn't work with
API permissions are specified as keywords, and each keyword names a WebExtension API that the extension would like to use.
The following keywords are currently available:
In most cases the permission just grants access to the API, with the following exceptions:
tabsgives you access to privileged parts of the
Tab.faviconUrl. In Firefox, you also need
tabsif you want to include
tabs.query(). The rest of the
tabsAPI can be used without requesting any permission.
webRequestBlockingenables you to use the "blocking" argument, so you can modify and cancel requests.
downloads.openlets you use the
This permission is specified as
"activeTab". If an extension has the
activeTab permission, then when the user interacts with the extension, the extension is granted extra privileges for the active tab only.
"User interaction" includes:
- the user clicks the extension's browser action or page action
- the user selects its context menu item
- the user activates a keyboard shortcut defined by the extension
The extra privileges are:
- access to the privileged parts of the tabs API for the current tab:
The intention of this permission is to enable extensions to fulfill a common use case, without having to give them very powerful permissions. Many extensions want to "do something to the current page when the user asks". For example, consider an extension that wants to run a script in the current page when the user clicks a browser action. If the
activeTab permission did not exist, the extension would need to ask for the host permission
<all_urls>. But this gives the extension more power than it needs: it could now execute scripts in any tab, any time it likes, instead of just the active tab and just in response to a user action.
There are two permissions which enables the extension to interact with the clipboard:
clipboardWrite: write to the clipboard using
clipboardRead: read from the clipboard using
See Interact with the clipboard for all the details on this.
Request privileged access to pages under developer.mozilla.org.
Request access to the privileged pieces of the
"permissions": ["*://developer.mozilla.org/*", "tabs"]
Request both of the above permissions.
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Chrome||Edge||Firefox||Firefox for Android||Opera|