Nos bénévoles n'ont pas encore traduit cet article en Français. Inscrivez-vous et aidez-nous à réaliser cette tâche !
Vous pouvez également lire cet article en English (US).
The Permissions API provides a consistent programmatic way to query the status of API permissions attributed to the current context — for example whether permission to use the API is granted or denied, and whether the user will be asked whether permission should be granted for an API.
Concepts and usage
Historically different APIs handle their own permissions inconsistently — for example the Notifications API allows for explicit checking of permission status and requesting permission, whereas the Geolocation API doesn't (which causes problems if the user denied the initial permission request). The Permissions API provides the tools to allow developers to implement a better user experience as far as permissions are concerned.
permissions property has been made available on the
Navigator object, both in the standard browsing context and the worker context (
WorkerNavigator — so permission checks are available inside workers), and returns a
Permissions object that provides access to the Permissions API functionality.
Once you have this object you can then perform permission-related tasks, for example querying a permission using the
Permissions.query() method to return a promise that resolves with the
PermissionStatus for a specific API.
At the time of writing, only the
Geolocation, Notifications, Push , and WebMIDI APIs are recognised by the Permissions API, with Chrome only including the first two. This list will grow as the API is implemented further.
Read more about how it works in our article Using the Permissions API.
- Provides access to the
Permissionsobject from the main context and worker context respectively.
- Provides the core Permission API functionality, such as methods for querying and revoking permissions.
- Provides access to the current status of a permission, and an event handler to respond to changes in permission status.
|Permissions||Working Draft||Initial definition.|
We're converting our compatibility data into a machine-readable JSON format. This compatibility table still uses the old format, because we haven't yet converted the data it contains. Find out how you can help!
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari (WebKit)|
|Basic support||43.0||46 (46)||?||?||?|
|Feature||Android||Android Webview||Firefox Mobile (Gecko)||IE Phone||Opera Mobile||Safari Mobile||Chrome for Android|
|Basic support||No support||43.0||46.0 (46)||?||?||?||43.0|