W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2014

Re: [whatwg] Preventing wake lock leaks with DOM nodes

From: Marcos Caceres <w3c@marcosc.com>
Date: Mon, 18 Aug 2014 20:33:08 -0400
To: Domenic Denicola <domenic@domenicdenicola.com>
Message-ID: <D1D63F537A814BE88BA5A69B9B05F21B@marcosc.com>
Cc: WHAT Working Group <whatwg@lists.whatwg.org>



On Monday, August 18, 2014 at 8:10 PM, Domenic Denicola wrote:

> In general I feel this thread has taken a turn for the complex. Why don't we just do what other platforms do, and provide a simple global request/release mechanism (or toggleable Boolean property!), which developers can build on top of? A lot of the ideas here seem to be trying to create the perfect, developer-friendly, foolproof API. Some of them seem quite clever too, tying to page visibility and the like. But all of them could be built, as libraries, on top of a global request/release. That way users could get reference counting if they want that, visibility-based locking if they want that, promise-based locking if they want that, timeouts if they want those, or even just not do any of those if their use case is simple enough that it doesn't warrant anything more complicated than what they are already doing on existing platforms.


 
> 
> We don't need to solve Hard Problems in Programming (TM) before we expose a wake lock API. Leave that as a subsequent step, which users can do, while we move on to exposing more missing platform capabilities 
Received on Tuesday, 19 August 2014 00:33:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:22 UTC