W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2017

RE: [wake-lock] Candidate Rec blockers

From: Lin, Wanming <wanming.lin@intel.com>
Date: Wed, 18 Oct 2017 10:20:44 +0000
To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "W3C Devices and Sensors WG" <public-device-apis@w3.org>
Message-ID: <0661EB478D420148A97FAFA1DEEBBC3B542F7A2D@SHSMSX103.ccr.corp.intel.com>
Hi, Anssi

> * There are no web-platform-tests [4] for Wake Lock API. It is strongly
> recommended to ship at minimum a preliminary test suite along with a CR spec.
> Blink's tests could be potentially used as a starting point, but would need to be
> reworked to align with the latest spec.

I am the volunteer. I will start to create the test suite with Web IDL tests.
Of cause, other contributions are encouraged.:-)

Thanks,
Wanming

> -----Original Message-----
> From: Kostiainen, Anssi [mailto:anssi.kostiainen@intel.com]
> Sent: Wednesday, October 18, 2017 3:27 PM
> To: W3C Devices and Sensors WG <public-device-apis@w3.org>
> Subject: [wake-lock] Candidate Rec blockers
> 
> Hi,
> 
> At our latest teleconference, we charted a plan [1] to transition Wake Lock API
> [2] to Candidate Recommendation.
> 
> Looking into this, I have identified two issues for which we need clarity on prior
> to asking for a transition to CR, in particular, with respect to the following
> transition requirement [3]:
> 
> [[
> 
> * must document how adequate implementation experience will be
> demonstrated
> 
> ]]
> 
> The issues identified are the following:
> 
> * There are no web-platform-tests [4] for Wake Lock API. It is strongly
> recommended to ship at minimum a preliminary test suite along with a CR spec.
> Blink's tests could be potentially used as a starting point, but would need to be
> reworked to align with the latest spec.
> 
> * The only known implementation [5] is based on an earlier version of the
> specification. The specification was since reworked substantially and the
> implementation is no longer aligned. We'd need to demonstrate these changes
> are implementable, or that they will not cause difficulty of implementation.
> 
> We're looking for volunteers to help with the above-mentioned tasks to allow
> the Wake Lock API spec to advance to CR.
> 
> Thanks,
> 
> -Anssi (Device and Sensors Working Group Chair)
> 
> [1] https://www.w3.org/2017/10/05-dap-minutes.html#action03
> [2] https://w3c.github.io/wake-lock/
> [3] https://www.w3.org/2017/Process-20170301/#candidate-rec
> [4] https://github.com/w3c/web-platform-tests/
> [5] https://crbug.com/257511
> 
Received on Wednesday, 18 October 2017 10:21:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:10 UTC