You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lastLocation() on the web was temporarily implemented here #211 by getting current location. Ideally, it should get the last known location, like Android and iOS.
The text was updated successfully, but these errors were encountered:
Preface this with the fact that I'm not a web developer by any means. But It sounds like the current API being used might be the right approach.
Setting the maximumAge might be what we want to add:
A positive long value indicating the maximum age in milliseconds of a possible cached position that is acceptable to return. If set to 0, it means that the device cannot use a cached position and must attempt to retrieve the real current position. If set to Infinity the device must return a cached position regardless of its age. Default: 0.
And possibly use a short timeout interval so that it will return early if no location exists.
I'm not a web developer either, just a name of the function on the web didn't sound to me like it gets the last location, but if you think it's the right approach, feel free to close the issue.
I wouldn't set the maximumAge here, as by definition, the last location can be stale, and that's okay, it's the user's responsibility to take care of it, as we have a timestamp with every location.
lastLocation()
on the web was temporarily implemented here #211 by getting current location. Ideally, it should get the last known location, like Android and iOS.The text was updated successfully, but these errors were encountered: