Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Geolocation using Generic Sensor API #36

Closed
marcoscaceres opened this issue Oct 9, 2017 · 2 comments · Fixed by #399
Closed

Geolocation using Generic Sensor API #36

marcoscaceres opened this issue Oct 9, 2017 · 2 comments · Fixed by #399
Labels
position: negative venue: W3C Specifications in W3C Working Groups

Comments

@marcoscaceres
Copy link
Contributor

marcoscaceres commented Oct 9, 2017 •
edited by annevk
Loading

Request for Mozilla Position on an Emerging Web Specification

Other information

Geolocation API refactored to use Generic Sensor spec.
@marcoscaceres marcoscaceres changed the title RPF: Geolocation using Generic Sensor API RFP: Geolocation using Generic Sensor API Oct 9, 2017
@marcoscaceres marcoscaceres mentioned this issue Oct 9, 2017
Closed
@hsivonen
Copy link
Member

The intro says this enhances privacy and security. How exactly? What problem does this solve beyond making geolocation looks like other sensors API-wise?

@dbaron dbaron added the venue: W3C CG Specifications in W3C Community Groups (e.g., WICG, Privacy CG) label Aug 9, 2018
@voxpelli voxpelli mentioned this issue Jun 30, 2020
Closed
@annevk annevk added venue: W3C Specifications in W3C Working Groups and removed venue: W3C CG Specifications in W3C Community Groups (e.g., WICG, Privacy CG) labels Jul 21, 2020
annevk added a commit that referenced this issue Jul 21, 2020
@annevk
Add Geolocation Sensor (harmful)
5bd756d 
Closes #36.
@annevk annevk mentioned this issue Jul 21, 2020
Merged
@annevk
Copy link
Contributor

annevk commented Jul 22, 2020

It does not appear to solve a problem in that space as far as I can tell. And as discussed in #35 it's not clear sensors need a generic API. I've suggested we close this as harmful in #399 with this rationale:

Given that the web already has a geolocation API, any additional API for the same purpose would have to meet a high bar as both will need to be maintained forever. While the document claims to improve security and privacy, there is no evidence that is the case. And as it can be largely polyfilled on top of the existing API, it seems better to invest in web platform geolocation additions there, if any.

annevk added a commit that referenced this issue Jul 23, 2020
@annevk
Add Geolocation Sensor (harmful)
f549ccf 
Closes #36.
annevk added a commit that referenced this issue Jul 23, 2020
@annevk
Add Geolocation Sensor (harmful)
326d719 
Closes #36.
@marcoscaceres marcoscaceres mentioned this issue Jul 11, 2022
Closed
@jgraham jgraham mentioned this issue Sep 7, 2023
Closed
@zcorpan zcorpan changed the title RFP: Geolocation using Generic Sensor API Geolocation using Generic Sensor API Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
position: negative venue: W3C Specifications in W3C Working Groups
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Geolocation Sensor (harmful) mozilla/standards-positions
5 participants
@zcorpan @dbaron @hsivonen @marcoscaceres @annevk