Is the "wakelock" API exposed to content on desktop Firefox? It seems very phone/B2G specific at the moment.
Strictly from a desktop/content perspective, it would be handy if the API to disable the screensaver was exposed as a simple CSS property, much like the cursor:none CSS property.
Then I could have a simple rule such as:
video:-moz-full-screen {
screen-saver: none;
}
And then not have to worry about the screen saver kicking in while watching a full-screen video.
Or even something more general like:
video:not(paused) {
screen-saver: none;
}
It's considerably easier to implement this functionality compared to munging around in C++ (or JS even) to toggle the screen saver at the appropriate times.
This also means web developers (and us implementers!) don't need to remember to unlock() or (re)enableScreenSaver() when the screen-saver-disabled document has been gc'd; it happens automatically when the rule no longer applies.
Is the "wakelock" API exposed to content on desktop Firefox? It seems very phone/B2G specific at the moment.
Strictly from a desktop/content perspective, it would be handy if the API to disable the screensaver was exposed as a simple CSS property, much like the cursor:none CSS property.
Then I could have a simple rule such as:
video:- moz-full- screen {
screen-saver: none;
}
And then not have to worry about the screen saver kicking in while watching a full-screen video.
Or even something more general like:
video:not(paused) {
screen-saver: none;
}
It's considerably easier to implement this functionality compared to munging around in C++ (or JS even) to toggle the screen saver at the appropriate times.
This also means web developers (and us implementers!) don't need to remember to unlock() or (re)enableScree nSaver( ) when the screen- saver-disabled document has been gc'd; it happens automatically when the rule no longer applies.