Closed Bug 677256 Opened 8 years ago Closed 8 years ago
Migrate to Google Location Service v2
Google is implementing a simpler GLS service and deprecating the old one. We will migrate.
This file replaces the existing NetworkGelocationProvider.js. It is probably best to just review this file as the diff is going to be huge. I removed HELD support. I contacted the contributor and he is fine with it and will probably make an Add-on. Because of the large code change, I reintented everything to 2 space. The last file was a mess.
Assignee: nobody → doug.turner
Attachment #551470 - Flags: review?(ben)
This may need to be looked at by the security/privacy teams adding kw: sec-review-needed so we can triage the bug and decide yes/no.
Some web developers may have been using undocumented geo features that are going away with this update. We should probably add that to the "what's important for web developers" document for the release that carries this change.
ben, this is mostly the same as the file, but now in diff form. I updated the tests to be compatible with the new format, and included a tri-lic header.
spoke to dougt earlier and confirmed the new version of the api does not introduce any new security or privacy risks compared to the existing one in use, and in fact sends back less data. removing sec-review-needed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla9
(In reply to Doug Turner (:dougt) from comment #0) > Google is implementing a simpler GLS service and deprecating the old one. > We will migrate. Is that one still only for use of Firefox or can this one be used more publicly? Just wondering if this could give bug 494421 some traction...
Mozilla Firefox only.
(In reply to Doug Turner (:dougt) from comment #9) > Mozilla Firefox only. OK, thanks, just wanted to clarify that.
Anyone aware of anything in particular that I should be documenting here? Is just saying that the back-end service has been updated enough, or are there specific details that need mentioning?
The new scheme unconditionally appends "?browser=firefox&sensor=true" to the end of geo.wifi.uri, which breaks manually setting that pref to a data uri to force a particular location. In my case I don't have wifi on this computer so I want to override the IP based detection with something more accurate. Is there a workaround?
You need to log in before you can comment on or make changes to this bug.