HERE location does not work in browser, but works in osmtouch
Bug #1371166 reported by
Alexander Sack
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Fix Released
|
Critical
|
Olivier Tilloy | ||
1.2 |
Fix Released
|
Critical
|
Olivier Tilloy | ||
qtubuntu-sensors |
Fix Released
|
Critical
|
Olivier Tilloy | ||
webbrowser-app |
Invalid
|
Critical
|
Unassigned | ||
qtubuntu-sensors (Ubuntu) |
Fix Released
|
Undecided
|
Olivier Tilloy |
Bug Description
On my N4 I can use our HERE provider to get a location fix using latest utopic image. I cannot get this to work in any browser maps (e.g. here.com maps.google.com etc.).
Filing this bug to have this on our radar.
Related branches
lp:~osomon/oxide/geolocation-doesnt-like-nans
- Chris Coulson: Approve
-
Diff: 113 lines (+32/-5)4 files modifiedqt/core/browser/oxide_qt_location_provider.cc (+21/-5)
qt/tests/mock/position/source.cc (+9/-0)
qt/tests/mock/position/source.h (+1/-0)
qt/tests/qmltests/core/tst_geolocation.qml (+1/-0)
lp:~osomon/qtubuntu-sensors/shield-against-nans
- Loïc Minier: Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 37 lines (+12/-6)1 file modifiedplugins/position/core_geo_position_info_source.cpp (+12/-6)
summary: |
- location does not work in browser, but works in osmtouch + HERE location does not work in browser, but works in osmtouch |
Changed in webbrowser-app: | |
importance: | Undecided → Critical |
tags: | added: rtm14 |
tags: | added: touch-2014-09-25 |
Changed in qtubuntu-sensors: | |
assignee: | Thomas Voß (thomas-voss) → Olivier Tilloy (osomon) |
status: | Invalid → In Progress |
Changed in oxide: | |
milestone: | none → 1.2.2 |
status: | In Progress → Fix Released |
Changed in qtubuntu-sensors (Ubuntu): | |
status: | Confirmed → In Progress |
assignee: | nobody → Olivier Tilloy (osomon) |
Changed in oxide: | |
milestone: | 1.2.2 → branch-1.3 |
Changed in qtubuntu-sensors: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
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. getCurrentPosit ion() 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.