- From: tangobravo via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Feb 2019 09:40:23 +0000
- To: public-geolocation@w3.org
@othermaciej Thanks for the responses here. > Just to be clear about the current state of the beta: the feature is currently disabled by default everywhere unless the user manually turns on the user preference. If we had per-site permission, then that would take priority over the setting. Thanks for clarifying the current state. For the full 12.2 release you have (at least) 3 options: 1) Keep things as in the beta: many sites stop working, not many users would go through the hassle of turning on the option, horrible UX to talk users through the process. 2) Switch the default setting to be enabled: gives time for more discussion whilst still allowing privacy-conscious users to turn it off. [I'd throw in implementing other less-impactful mitigations in this option too, but given timeframes I think that is unlikely.] 3) Keep the default disabled but implement a permission request API: "progressive enhancement" use cases likely break, but those that require this API (360 photos etc) would be able to adapt. **I would strongly advocate for option 2 or 3.** Sorry for hijacking the bug for continuing this discussion. WebKit (rightly IMHO) don't consider it their bug, and the private nature of Apple's bug tracker shuts down discussion and prevents the web community from demonstrating the strength of feeling on this issue. -- GitHub Notification of comment by tangobravo Please view or discuss this issue at https://github.com/w3c/deviceorientation/issues/57#issuecomment-459951127 using your GitHub account
Received on Saturday, 2 February 2019 09:40:24 UTC