> That's the point of wake locks, to prevent the screen from being turned off.
I thought the point was to prevent the screen from being turned off *due to idle* -- that is, "wake" refers to keeping the screen from falling asleep.
> I think it makes more sense for wake
> locks to "win", since a conformant (privileged) user of screen.enabled wouldn't
> try to turn off the screen if there are wake locks, anyway. Or at least,
> wouldn't expect it to turn off.
What if a random page holds a screen-enabled wake-lock and I press the device's power button? We politely ask that app to let go of its wake-lock and then kill it if it doesn't? It seems much simpler just to turn off the screen. Ditto for the device's radio.
> That's the point of wake locks, to prevent the screen from being turned off.
I thought the point was to prevent the screen from being turned off *due to idle* -- that is, "wake" refers to keeping the screen from falling asleep.
> I think it makes more sense for wake
> locks to "win", since a conformant (privileged) user of screen.enabled wouldn't
> try to turn off the screen if there are wake locks, anyway. Or at least,
> wouldn't expect it to turn off.
What if a random page holds a screen-enabled wake-lock and I press the device's power button? We politely ask that app to let go of its wake-lock and then kill it if it doesn't? It seems much simpler just to turn off the screen. Ditto for the device's radio.