The Permissions API is marked as an experimental technology.
The issue is that Firefox does have navigator.permissions
and support the query
method on it, too, however, it does not support all the permission names that are listed on MDN's Permissions API page.
You can try this yourself: go to the console on Firefox and execute
// geolocation is working fine
navigator.permissions.query({ name: 'geolocation' }).then(console.log)
// camera, microphone is not supported, throws
navigator.permissions.query({ name: 'camera' })
// TypeError: 'name' member of PermissionDescriptor 'camera' is not a valid value for enumeration PermissionName.
navigator.permissions.query({ name: 'microphone' })
// TypeError: 'name' member of PermissionDescriptor 'microphone' is not a valid value for enumeration PermissionName.
There is an open discussion on Github in the mozilla/standards-positions
about their position on the Permissions API. To be honest, as I see, they did not reach any conclusion yet.
What you can do is you create a basic functionality that works on all browsers without the permissions information and on Chrome, you progressively enhance the user experience by using the Permissions.query
for figuring out the permissions for camera and microphone.
Alternatively, you can come up with some logic to handle this using MediaDevices.getUserMedia
: for example, you can call getUserMedia
and immediately stop the tracks, if the only thing you want is to ensure you app has permissions granted for microphone and camera. Be careful though, there are multiple problems with this:
- the camera light will be turned on for a second
- if your user denies permission, you will have a hard time asking for it again, so before you ask for permission, you should clarify to your users why you need these permissions
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…