> Use a setting.
> Maybe use a setting, but I'm not sure this needs to be configurable.
> Maybe setting, maybe hard code.
YAGNI -- no need to add isWakeLockHeld() now if you don't think you're going to need it. But it seems to me that we shouldn't design around specifically *not* allowing Gaia to determine whether a wake-lock is held, especially given our constraint of writing as much code in JS as possible.
(Using kernel code that already exists sounds fine to me. I just don't know why we'd opt to write something new in Gecko rather than in JS.)
> Use a setting.
> Maybe use a setting, but I'm not sure this needs to be configurable.
> Maybe setting, maybe hard code.
YAGNI -- no need to add isWakeLockHeld() now if you don't think you're going to need it. But it seems to me that we shouldn't design around specifically *not* allowing Gaia to determine whether a wake-lock is held, especially given our constraint of writing as much code in JS as possible.
(Using kernel code that already exists sounds fine to me. I just don't know why we'd opt to write something new in Gecko rather than in JS.)