Closed Bug 989719 Opened 6 years ago Closed 6 years ago
js error in Wifi
Worker when doing geolocation and Wi Fi is disabled
blocking-b2g: --- → 1.4?
Version: 30 Branch → Trunk
What build ID was this tested on? Was this tested with a build containing bug 986349?
(In reply to Jason Smith [:jsmith] from comment #1) > What build ID was this tested on? Was this tested with a build containing > bug 986349? Ah - missed the part saying "current gecko." Okay, that's today's build, which should have bug 986349.
Might be a regression from bug 976452. Leaving qawanted to confirm on Buri 1.4.
(In reply to Jason Smith [:jsmith] from comment #1) > What build ID was this tested on? Was this tested with a build containing > bug 986349? Yes.
adjusting and scoping this bug.
Summary: Geolocation broken when WiFi disabled → js error in WifiWorker when doing geolocation and WiFi is disabled
Comment on attachment 8399198 [details] [diff] [review] Patch v1.0 Review of attachment 8399198 [details] [diff] [review]: ----------------------------------------------------------------- Nice catch, Thanks!
Attachment #8399198 - Flags: review?(chulee) → review+
Blocked to test it, Geo-location doesn't work with on Buri device see bug 98481 1.4 Environmental Variables: Device: Buri 1.4 MOZ BuildID: 20140331000202 Gaia: 4c3b2f57f4229c5f36f0d8fd399e65f4db88f104 Gecko: 3aaca223b673 Version: 30.0a2 Firmware Version: v1.2-device.cfg
(In reply to sarsenyev from comment #8) > Blocked to test it, Geo-location doesn't work with on Buri device see bug > 98481 This isn't right. You need to have a SIM on your device & be outdoors to get geolocation to work.
The bug reproduces on Buri 1.5 central Geolocation shows incorrect location when WIFI is off Also I followed steps in comment 9 (SIM card inserted and outdoor), but Geo-location doesn't work on 1.4 and 1.3,the error message notifies "Can't find your location" 1.5 Environmental Variables: Device: Buri 1.5 MOZ BuildID: 20140331040200 Gaia: 26839cb46f856d610b192f5655a8c38a6bfe0829 Gecko: d8e8f13bd4ae Version: 31.0a1 Firmware Version: v1.2-device.cfg
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.