Closed
Bug 1022463
Opened 7 years ago
Closed 7 years ago
Use 10 seconds as the max time to wait for GPS data before using MLS
Categories
(Core :: DOM: Geolocation, defect)
Core
DOM: Geolocation
Tracking
()
People
(Reporter: dougt, Assigned: dougt)
References
Details
Attachments
(1 file)
1.30 KB,
patch
|
kanru
:
review+
|
Details | Diff | Splinter Review |
Currently we are seeing fluxuatoin between GPS derived data and MLS data due to a very short timeout (kDefaultPeriod == 1s). Basically what is happening is GPS sometimes takes more than 1 second to return a position. In this case, we might switch back to providing a MLS location. We should use something longer than 1s. I have been playing around with 5-10 seconds and do not see this flux problem any longer. I am picking 10s mostly because I want to give GPS as much possible time before hititng MLS for a much less accurate position.
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8436645 -
Flags: review?(josh)
Updated•7 years ago
|
Attachment #8436645 -
Flags: review?(josh) → review+
Assignee | ||
Comment 2•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/0ae930b73fd5
Comment 3•7 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0ae930b73fd5
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
Assignee | ||
Updated•7 years ago
|
blocking-b2g: --- → 1.4?
Updated•7 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Updated•7 years ago
|
Blocks: mls-dolphin
Updated•7 years ago
|
blocking-b2g: 1.4? → 1.4+
Comment 4•7 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/e4bad0e3a42a
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
status-firefox31:
--- → wontfix
status-firefox32:
--- → fixed
status-firefox33:
--- → fixed
Comment 5•7 years ago
|
||
Doug: did you forget to land this 1.4+ fix on the mozilla-b2g30 branch?
Flags: needinfo?(dougt)
Comment 6•7 years ago
|
||
Doug: Ryan says you need to rebase this patch for 1.4.
You need to log in
before you can comment on or make changes to this bug.
Description
•