If you're looking for an alternative to the Permissions API's navigator.permissions.query method, you might have specific requirements or compatibility issues with certain browsers or environments.

One alternative approach is to use feature detection or polyfills to check for permissions or implement fallback behavior.

Here are a few alternative methods:

  1. Feature Detection: Instead of relying on navigator.permissions.query, you can check if the desired feature is available directly. For example, you can use feature detection to check if geolocation is available:
if ('geolocation' in navigator) {
  // Geolocation feature is available, proceed with your logic
} else {
  // Geolocation feature is not available, handle accordingly
  1. Use fallback methods: Implement fallback methods or user prompts if the feature is not available. For example, if you need camera access:
if ('mediaDevices' in navigator && 'getUserMedia' in navigator.mediaDevices) {
  // Use navigator.mediaDevices.getUserMedia for camera access
} else {
  // Fallback method or prompt for user permission

Choose the alternative method that best suits your application's requirements and compatibility constraints.

You can use the following JavaScript code to check the permission status for accessing the microphone:

navigator.permissions.query({name:'microphone'}).then(function(result) {
  if (result.state === 'granted') {
    // Microphone access granted
  } else if (result.state === 'denied') {
    // Microphone access denied

You can use the Cordova diagnostic plugin, specifically the getLocationAuthorizationStatus method, which should return the permission state in a very similar way to the Permissions API.

The alternative for Safari browser to Navigator.permissions is using navigator.geolocation.getCurrentPosition. If it triggers the success callback, it means the user has granted access to their location.