Comment 92 for bug 604635

(In reply to Justin Lebar [:jlebar] from comment #57)
> > It's not really a question of simplicity, but API semantics. Let's nail that down first.
>
> What I mean is, it's a much simpler API if pages don't have to listen for
> "wake lock going away" and explicitly release the wake lock. Simpler APIs
> are preferable to complex APIs, because there's less room for error, and
> every mistake which can be made will be made, and by many pages.
>
> I think the API should have advisory wake-locks; that is, when I call
> screen.enabled = false, the screen turns off, period.
>

Not to sound too much like a broken record, but what does android do?