- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2017 07:52:09 +0000
- To: public-device-apis-log@w3.org
Revisiting this issue after some thought, I now feel the low/high precision mode and related machinery should not be exposed to the web developer direct. I'm not yet sure whether allowing some implementers to toggle such a mode as a side-effect of a [permission state] would be a smart thing to do or whether that would in fact lead to interoperability issues across implementations. @reillyeon you said: >there should be a well defined interface for determining whether the user has granted permission for high-resolution mode Did you mean the granted [permission state] could be taken as a hint for high precision, or that an explicit extension to the [permission descriptor] à la the [enableHighAccuracy] flag of the Geolocation API should be added? If the latter, I'd like to understand how well that has worked in real life for geo and what the web developer feedback has been to date. My recollection is there has been issues with it, but I don't have a pointer at hand to backup my claim. [permission state]: https://w3c.github.io/permissions/#permission-state [permission descriptor]: https://w3c.github.io/permissions/#dictdef-permissiondescriptor [enableHighAccuracy]: https://www.w3.org/TR/geolocation-API/#high-accuracy -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/sensors/issues/183#issuecomment-299797727 using your GitHub account
Received on Monday, 8 May 2017 07:52:16 UTC