Comment 1 for bug 1371166

I’ve spent most of my day testing this, trying to reproduce failures, and the results are not consistent from one test run to the other (i.e. it sometimes works, sometimes not). By instrumenting oxide and qtubuntu-sensors though, I was able to determine that oxide calls in to the positioning plugin as expected, but the plugin does not always answer.

It’s likely that google maps and here.com issue a call to navigator.geolocation.getCurrentPosition() with a timeout parameter, so if the plugin takes too long to answer (or never does), the timeout is hit and the pages report that they were unable to determine the location. For comparison, http://html5demos.com/geo does not specify a timeout, so it sits there waiting for an answer forever (and sometimes eventually gets it, sometimes not).

The bug is not in webbrowser-app, and unlikely to be in oxide either, but I’m not sure where to target it.