W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2016

Re: [wake-lock] Wake Lock API status update

From: Mounir Lamouri <mounir@lamouri.fr>
Date: Thu, 21 Jan 2016 12:34:38 +0000
Message-Id: <1453379678.3045696.498503802.6F57E6A7@webmail.messagingengine.com>
To: Frederick Hirsch <w3c@fjhirsch.com>, Marcos Caceres <w3c@marcosc.com>
Cc: W3C Device APIs WG <public-device-apis@w3.org>, "Dominique Hazael-Massieux" <dom@w3.org>
Do we need implementations or shipping implementations? I do not know if
the Yandex browser ships the API but the API is not enabled by default
in Chromium's builds.

-- Mounir

On Tue, 19 Jan 2016, at 19:03, Frederick Hirsch 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 12:35:13 UTC

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