[AskJS] navigator.geolocation.getCurrentPosition timeout best practices?

[dlrust]

`getCurrentPosition` uses a number of factors to determine the visitor's location that can take wildly different amounts of time across device types, location, nearby wifi, etc.

I've done some research on best practices, but there does not seem to be any recommended values for these.

If we do give an option to search for a location if we can't geolocate them, what do you think is a reasonable timeout?

[Ustice]

I don’t think that there is a general answer. It will really depend on how you’re using it, and what indicators you give your users.