- From: Fuqiao Xue <xfq@w3.org>
- Date: Wed, 24 Jun 2020 11:04:00 +0800
- To: public-apa@w3.org
- Cc: anssi.kostiainen@intel.com, reillyg@google.com
Hi, The Devices and Sensors WG plan to publish a new REC of the Geolocation API Specification. Here's the current ED: https://w3c.github.io/geolocation-api/ This specification defines an API that provides scripted access to geographical location information associated with the hosting device. It is now maintained by the Devices and Sensors WG, and contains the following substantive changes since the last REC: - Now Controlled by feature policy - Fixed confusion around callback interfaces not being an EventHandler - Only expose the API in SecureContexts - Renamed the interfaces and dictionaries + removal of [NoInterfaceObject] + [SameObject] annotation on geolocation attribute I have worked through the FAST Checklist and this specification: * defines an API * does not allow visual rendering of content * does not provide author control over color * does not provide features to accept user input * does not provide user interaction features * does not define document semantics * does not provide time-based visual media * does not provide audio * does not allow text content * does not create objects that don't have an inherent text representation * does not provide visual graphics * allows time limits (see the timeout and maximumAge attributes in the PositionOptions[1] dictionary) Most of the accessibility concerns are tangential to this spec, but if you do find any issues, please file them at https://github.com/w3c/geolocation-api/issues Thanks, Fuqiao [1] https://w3c.github.io/geolocation-api/#position_options_interface
Received on Wednesday, 24 June 2020 03:04:02 UTC