- From: Lin, Wanming <wanming.lin@intel.com>
- Date: Tue, 15 Jan 2019 03:10:18 +0000
- To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "W3C Devices and Sensors WG" <public-device-apis@w3.org>
Hi, Anssi > On January 14, 2019 6:29 PM, Kostiainen, Anssi <anssi.kostiainen@intel.com> > wrote: > > Hi All, Wanming, > > > On 5 Dec 2018, at 12.22, Kostiainen, Anssi <anssi.kostiainen@intel.com> > wrote: > > > >> On 27 Nov 2018, at 11.22, Kostiainen, Anssi <anssi.kostiainen@intel.com> > wrote: > >> > >> I'm pleased to announce the first version of the WebDriver Extension API for > Generic Sensor has landed: > >> > >> https://w3c.github.io/sensors/webdriver-extension/ > >> > >> You'll also find the extension API from the DAS WG's roadmap: > >> > >> https://www.w3.org/das/roadmap > >> > >> Per abstract, this document defines extension commands to the WebDriver > specification for the purposes of testing a user agent’s implementation of > Generic Sensor API and its concrete Sensor APIs. > >> > >> Thanks Wanming for leading and editing WebDriver Extension API for Generic > Sensor spec, as well as to contributors Raphael, jugglinmike, Philip, John Chen, > others for reviews, feedback and comments. > > > > The chairs suggest the group integrates the Web Driver Extension API into the > Generic Sensor API after the extension spec has been stabilized for a while as an > Editor's Draft. > > > > This means the Generic Sensor API will be published as a revised CR with the > extension spec integration that triggers another wide review. However, we > believe the wide review can be limited to new features, and we can skip security > and privacy reviews since the extension API does not expose new features to the > Web. Similarly, we believe we can skip accessibility and internationalization > reviews since they are not relevant to the extension spec. > > > > We will, however, seek review from the Browser Testing and Tools Working > Group responsible for the WebDriver spec. > > > > Please let us know if you have any concerns with the proposed plan by EOY. I'd > > expect this integration work to commence earliest Q1 2019. > > No concerns were raised. We can start integrating the WebDriver extension API > into the Generic Sensor API unless there are open issues/PRs in flight that'd be > easier to address in the standalone spec first. > > Wanming - I see one open issue for the extensions API > https://github.com/w3c/sensors/issues/371 but it seems to be v2 feature. > Correct? Any other open issues we should address prior to starting the > integration work? Many thanks for moving this forward! Yes, this should be a v2 feature, depending on request from real web developers that attempting to use this proposed feature. And I have one open issue in mind, the spec introduces new WebDriver errors[1], but WebDriver support[2] for new error types is still pending, Would this be a blocker for the integration work? [1] https://w3c.github.io/sensors/webdriver-extension/#extension-handling-errors [2] https://github.com/w3c/webdriver/issues/1151 Thanks, Wanming
Received on Tuesday, 15 January 2019 03:10:46 UTC