No, I mean adding a "use your location" button yourself which the user has to click before it uses the geolocation API, rather than just blindly requesting it on page load.
The only reason people block it in settings is because they get sick of nagging prompts they never asked for.
Ah, gotcha. So this change is giving developers a more standardised way to follow that "add a button, pop up permission dialog" pattern that will hopefully drive more of them away from the bad pattern?
Isn't Frozen something you do to a set or dictionary to say, I'm not going to add any more values, please give me a version of this which is optimized for lookup only?
Does that mean identifying the browser and trying to tell the user how to go into the browser settings and un-block permission prompts?
reply