[wake-lock] next steps (was Wake Lock API status update)

I  misspoke, apologies. We need at least two implementations to *exit* CR.  Having one implementation going into CR is great!

On today's DAP call [1]  we discussed the following next steps for Wake Lock (Andrey was on the call)

1. Review open issues and close them (or note what should be kept open going into CR). Andrey is looking into this.

2. Update the document status section to note that the draft is stable and we are seeking review feedback (informal Last Call if you will) - Editors do this

3 Send out request for feedback to various parties, including W3C chairs, public review announce etc - I'll do this when ready

4. Then transition to CR - Dom and I will work on this

thanks

regards, Frederick

Frederick Hirsch
Chair, W3C Device APIs WG (DAP)

www.fjhirsch.com
@fjhirsch

[1] https://lists.w3.org/Archives/Public/public-device-apis/2016Jan/att-0062/minutes-2016-01-21.html


> On Jan 19, 2016, at 2:03 PM, Frederick Hirsch <w3c@fjhirsch.com> wrote:
> 
> Marcos
> 
> We need at least two implementations to move WakeLock forward to CR (and REC) based on the group's minimum CR exit criteria, preferably more.
> 
> It sounds like there is only one implementation at this point, Chromium.
> 
> How do you interpret the Firefox status (including the bug report which is for Firefox for Android)?
> 
> Thanks
> 
> regards, Frederick
> 
> Frederick Hirsch
> Chair, W3C Device APIs WG (DAP)
> 
> www.fjhirsch.com
> @fjhirsch
> 
>> On Jan 19, 2016, at 8:24 AM, Marcos Caceres <w3c@marcosc.com> wrote:
>> 
>> 
>> 
>> On January 20, 2016 at 12:19:09 AM, Dominique Hazael-Massieux (dom@w3.org) wrote:
>>> Hi Marcos,
>>> 
>>> On 11/01/2016 09:39, Андрей Логвинов wrote:
>>>> The Wake Lock API (http://www.w3.org/TR/wake-lock/) has been implemented
>>>> in Chromium as an experimental feature, available since version 48.0.2551.0.
>>> 
>>> Any visibility on if and when Firefox would adopt that API as a
>>> replacement to navigator.requestWakeLock()?
>> 
>> Not sure. I thought it was only supported in FxOS?  
>> 
>>> Is there an existing bug to track implementation progress in Firefox?
>> 
>> I did a quick search and only found this one:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1054113
>> 
>> 
>> 
>> 
> 
> 
> 
> 
>

Received on Thursday, 21 January 2016 15:50:05 UTC