Comment 44 for bug 604635

Revision history for this message
In , Chris Jones (jones-chris-g) wrote :

(In reply to Jonas Sicking (:sicking) from comment #11)
> I like disableScreenSaver/enableScreenSaver.
>
> The way I was thinking it'd work is similar to the vibrator API. We'd track
> separately for each page if it wants to have the screensaver
> enabled/disabled. Then we'd use the state of whichever page is the currently
> active page.
>

Agreed, except in this case I think we'd want to save and restore lock state for windows that go visible --> hidden --> visible. I think that's what you're proposing. We don't do that for vibrator because it's too hard.

> I don't really see any use cases for a background page to disable the screen
> saver. Can anyone else?
>

Nope. There are use cases for background windows disabling other power-saving features, though.