W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2014

Re: Standby API Specification Proposal

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Wed, 28 May 2014 13:41:11 +0000
To: Marcos <marcos@marcosc.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
CC: Frederick Hirsch <w3c@fjhirsch.com>, Dominique Hazael-Massieux <dom@w3.org>, Mats Wichmann <m.wichmann@samsung.com>
Message-ID: <F70C7C83-0798-4FF3-87B0-5D82143E3DA2@intel.com>
On 28 May 2014, at 15:54, Marcos <marcos@marcosc.com> wrote:

>> Is it possible that the browser implementation could detect  
>> window refresh associated with video or games, thus obviating  
>> the need for use of an API entirely in some cases? (that still would  
>> not address the use case of viewing a recipe)
> 
> You could, like assuming requestAnimationFrame() or CSS animations could imply this. But it's a bit of an abuse of the API and would tie people to using some particular solution or another. That could become unpredictable and have unforeseen consequences that developers didn't expect ("wtf is causing the screen to stay on?"). It's better, IMO, to let developers just handle this and not add any magic.    

Agreed. These would be considered side effects, which is bad. Also, each implementation would act differently.

Thanks,

-Anssi
Received on Wednesday, 28 May 2014 13:41:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:33:08 UTC