[prev in list] [next in list] [prev in thread] [next in thread] 

List:       whatwg
Subject:    Re: [whatwg] Preventing wake lock leaks with DOM nodes
From:       Jonas Sicking <jonas () sicking ! cc>
Date:       2014-08-19 1:20:58
Message-ID: CA+c2ei_BFtn6CKA9mD6PD7+k8zn=xXDR27VqdVQDHcZNMatHYw () mail ! gmail ! com
[Download RAW message or body]

On Mon, Aug 18, 2014 at 5:35 PM, Marcos Caceres <w3c@marcosc.com> wrote:
> The reason I didn't make it a boolean was because of the IPC involved and because I \
> wanted to support multiple types of locks without needing to add new attributes in \
> the future (and if we need to add the complex stuff later).

What's the problem with adding more attributes in the future?

That said, I do think that a "timeout" for screen locks make sense, so
a boolean wouldn't work. Though not as a timeout for when to release
the lock, but rather as a "minimum time I'd like to keep the screen
awake" as described at

http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-August/297423.html

/ Jonas


[prev in list] [next in list] [prev in thread] [next in thread]