Geolocation should be automatic on mapper frontend

[spwoodcock]

Describe the bug

• We avoided making geolocation automatic on the management frontend, as people only viewing the project wouldn't want this.
• The mapper frontend is specific to mapping, and the user will almost always want to geolocate.
• Current UX isn't great, where the user is expected to click a button - it's not intuitive like other map apps.

Solution

• Automatically start the geolocation when the mapnow page is loaded.

[manjitapandey]

When the mapnow page is loaded, the geolocation is on by default if I turn on my location beforehand. But when location is off, the chrome browser doesn't ask for the access rather shows the error message saying geolocation is denied.
I don't think this should be expected. Can we do anything that browser ask for permission instead of error message without asking?

[NSUWAL123]

There are two cases when the user device location is turned off:

1. Turning geolocation on via button click (implemented in management frontend)
   If the user accesses the website for the first time and hasn't touched the permissions of the website, then the permission popup is shown. If the user has already declined the permission request prior, then geolocation denied popup will be shown.
   

2. Automatic geolocation on (mapper frontend)
   Here since we automatically trigger the geolocation status to be turned on, due to security measures implemented by browsers, the permission popup will not be shown and the geolocation denied popup will be shown by the browsers by default although they are new users.

I think it's not possible to show the permission popup instead of an error. But we have to research the workarounds if there's any possibility.