W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2015

Re: [wake-lock] Wake Lock API Status request

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Thu, 25 Jun 2015 09:17:59 -0400
Cc: W3C Device APIs WG <public-device-apis@w3.org>
Message-Id: <F08ED6AA-7B9B-428B-8DA7-9BD529B33E2C@fjhirsch.com>
To: Андрей Логвинов <alogvinov@yandex-team.ru>
Andrey

Thank you for the update on the Wake Lock API. Yes, you are right, the FPWD is already published (I've been thinking about other groups publishing FPWD so mistakenly included this one)

When do you expect the upstreaming to be complete - what is involved now?

Are you able to share a test report? Is there any more that the WG can do at this point?

Thanks

regards, Frederick

Frederick Hirsch
Chair, W3C Device APIs WG (DAP)

www.fjhirsch.com
@fjhirsch



> On Jun 25, 2015, at 4:49 AM, Андрей Логвинов <alogvinov@yandex-team.ru> wrote:
> 
> Hello Frederick,
>  
> Sorry for late response. Wake Lock API as specified in http://www.w3.org/TR/wake-lock/ is implemented in Yandex Browser as an experimental feature, upstreaming to Chromium is currently in progress.
>  
> The implementation includes Javascript tests (which I guess are browser-neutral) and Chromium-specific internal tests.
>  
> We have identified no issues during implementation, but there's been some issues raised by other users at https://github.com/w3c/wake-lock/issues regarding the interface (e.g. whether it would be better to put the API to Screen or Window or Navigator instead of Document).
>  
> As for FPWD publication, I think this is already done at http://www.w3.org/TR/wake-lock/, or am I missing something?
>  
> Kind regards,
> Andrey Logvinov
>  
Received on Thursday, 25 June 2015 13:18:38 UTC

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