[FEATURE] geolocation permission

🚀 Feature request

Is your feature request related to a problem?

Having GEOLOCATION_SUPPORT injection token does not quite answer the question of whether the developer can use the geolocation Web API. The GEOLOCATION_SUPPORT simply checks if navigator.geolocation object is available. However, the user may have received the browser popup during one of the previous visits to the website and automatically clicked “Block” (like many of us do these days whenever any popup shows up). In this case, the GEOLOCATION_SUPPORT will resolve to true, but geolocation$ observable will emit an error.

Describe the solution you’d like

To answer the question of whether the user has allowed the website access to geolocation, we can run the following code:

navigator.permissions.query({ name: 'geolocation' }).then((x) => console.log(x.state))
// this will print "prompt", "denied", or "granted"

I wonder if an injection token GEOLOCATION_PERMISSION could be introduced that would run the code above under the hood? Given the fact that this API returns a Promise, I’m not sure if it can still be an Injection token or if it’ll have to be an observable service similar to the geolocation$

[Important] Something to keep in mind: the support for the API above is somewhat spotty: https://caniuse.com/permissions-api

Describe alternatives you’ve considered

Here people suggest using the second callback for the navigator.geolocation.watchPosition method that’s called upon an error. This does not really solve the issue for me because calling this function will trigger the popup and I would like to know whether the geolocation Web API is available before the popup shows up.

[IKatsuba]

I think we have to move up to Angular 9. Tomorrow Angular 8 LTS will end https://angular.io/guide/releases#support-policy-and-schedule

[DmitryEfimenko]

Created a PR for this: https://github.com/ng-web-apis/permissions/pull/1 I’m closing this issue. Let’s move our conversation into the PR.