Use Windows & Mac system API for geolocation
Categories
(Core :: DOM: Geolocation, defect)
Tracking
()
People
(Reporter: Sylvestre, Assigned: Sylvestre)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr60+
|
Details | Review |
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Comment 4•6 years ago
|
||
bugherder |
Comment 5•6 years ago
|
||
Assignee | ||
Comment 6•6 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Comment 7•6 years ago
|
||
Emil, has it been verified yet? Thanks
Comment 8•6 years ago
|
||
(In reply to Sylvestre Ledru [:sylvestre] from comment #7)
Emil, has it been verified yet? Thanks
Sorry for not updating things here sooner. Yes, Geolocation has been covered as part of the 65.0b7 sign off - Smoke and Regression Testing revealed no issues following this change.
Updated•6 years ago
|
Assignee | ||
Comment 9•6 years ago
|
||
No worries Andrei. thanks!
Assignee | ||
Comment 10•6 years ago
|
||
Comment on attachment 9029595 [details]
Bug 1512161 - Use Windows & Mac system API for geolocation r?jdm
ESR Uplift Approval Request
If this is not a sec:{high,crit} bug, please state case for ESR consideration
Not a security issue. We want to limit the traffic on the key by leveraging the system API on Windows & Mac
User impact if declined
Should be transparent for the user, this is for Mozilla
Fix Landed on Version
65
Risk to taking this patch
Low
Why is the change risky/not risky? (and alternatives if risky)
We shipped 65 with this change + we pushed an experiment changing that
String or UUID changes made by this patch
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 11•6 years ago
|
||
Comment on attachment 9029595 [details]
Bug 1512161 - Use Windows & Mac system API for geolocation r?jdm
Other than the one issue with the Windows key which we've already remedied, I'm not aware of any negative fallout from the recent Geolocation changes shipped in Fx65 and enabled for ESR60 via experiment. Let's go ahead and land this for 60.6.0 so that we're consistent across all releases and able to reduce our usage of the Google APIs.
Comment 12•6 years ago
|
||
bugherder uplift |
Assignee | ||
Comment 13•6 years ago
|
||
Andrei, it would be great if this could be verified
Thanks
Note that it isnt always enabled by default on windows
Updated•6 years ago
|
Comment 14•6 years ago
•
|
||
Verified geolocation on the latest 60.6esr build from taskcluster, no issues were found.
For 65 RC the geolocation tests were covered during the 65.0.2-build1 validation, no issues were encountered.
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Description
•