"Final" proposal. Please reply-to dev-weba...@lists.mozilla.org with any major
issues.
Name of API: Resource Lock API
Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=697132
Brief purpose of API: Prevent the screen from being dimmed or switched off
General Use Cases: Request a lock to st
I haven't seen any comments on this for a while so I'll be closing this out and
posting on Friday. Please send any last comments before noon PDT. Thanks!
Lucas.
On Apr 15, 2012, at 11:18 PM, Lucas Adamski wrote:
> Please reply-to dev-weba...@lists.mozilla.org
>
> Name of API: Resource Lock
On Apr 17, 2012, at 6:02 AM, Benjamin Smedberg wrote:
> On 4/16/2012 2:18 AM, Lucas Adamski wrote:
> Why can't we just let all content have access to this API by default, at
> least when it is in the foreground? I really don't think we need to make
> users choose whether websites can turn off th
> It would be great if the spec also specified that the phone needs to
> provide a resource consumption manager.
Perhaps "should" rather than "needs to". This is a non-trivial thing
to do, in general. Not that we shouldn't do it, but I don't think we
should say that we're in violation of the spe
It would be great if the spec also specified that the phone needs to
provide a resource consumption manager. That way concerned users could see
which trusted/certified apps are responsible for a short battery life, if
the phone is being drained too fast.
On Sun, Apr 15, 2012 at 11:18 PM, Lucas Ad
Please reply-to dev-weba...@lists.mozilla.org
Name of API: Resource Lock API
Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=697132
Brief purpose of API: Prevent the screen from being dimmed or switched off
General Use Cases: Request a lock to stop the screen from being dimmed, even if
t
