My theory was that a bug in the event loop was causing Chromium and iOS Safari to fail geolocation checks. Actually, it seems like the navigator.geolocation.getCurrentPosition() calls are not working on those platforms at all, and I need to diagnose things further.
My theory was that a bug in the event loop was causing Chromium and iOS Safari to fail geolocation checks. Actually, it seems like the
navigator.geolocation.getCurrentPosition()
calls are not working on those platforms at all, and I need to diagnose things further.