- From: Fuqiao Xue via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Aug 2020 02:29:00 +0000
- To: public-device-apis-log@w3.org
I wonder if this strategy is doable: focus on working on Geolocation Sensor, and polyfill on top of the Geolocation Sensor for Geolocation API, or produce a report if that's not possible. Currently there's a [polyfill](https://github.com/kenchris/sensor-polyfills/blob/master/src/geolocation-sensor.js) for Geolocation Sensor on top of the existing Geolocation API, but this suggestion is the reverse of that. The advantages of this approach is that we can work on the modern API with [improved security and privacy](https://w3c.github.io/sensors/#security-and-privacy), addresses [new use cases](https://w3c.github.io/geolocation-sensor/#use-cases), and the Geolocation API may not need to be maintained in the future (so there's no need to duplicate the effort). -- GitHub Notification of comment by xfq Please view or discuss this issue at https://github.com/w3c/dap-charter/issues/103#issuecomment-675212677 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 August 2020 02:29:01 UTC