(In reply to Edwin Flores [:eflores] [:edwin] from comment #57)
> (In reply to Martin Stránský from comment #53)
> > The screensaver should not be inhibited by "cpu" and "high-priority" wake
> > locks. It looks like those are used to inhibit GC or disable power save (see
> > Bug 872430).
>
> This isn't an issue with wake lock code, it's an issue with wake locks being
> used incorrectly on desktop. The better solution here would be to make sure
> that "cpu" and "high-priority" are never used in the first place, on desktop.
That's possible but we just can't disable screensaver for *any* lock, right? We want to disable it for the screen-related events only, not for audio events or so.
I see the "DOM_Fullscreen" should not be used here - It seems to be set for any fullscreen elements, like full-screen webgl canvas, full-screen browsing and so.
(In reply to Edwin Flores [:eflores] [:edwin] from comment #57)
> (In reply to Martin Stránský from comment #53)
> > The screensaver should not be inhibited by "cpu" and "high-priority" wake
> > locks. It looks like those are used to inhibit GC or disable power save (see
> > Bug 872430).
>
> This isn't an issue with wake lock code, it's an issue with wake locks being
> used incorrectly on desktop. The better solution here would be to make sure
> that "cpu" and "high-priority" are never used in the first place, on desktop.
That's possible but we just can't disable screensaver for *any* lock, right? We want to disable it for the screen-related events only, not for audio events or so.
I see the "DOM_Fullscreen" should not be used here - It seems to be set for any fullscreen elements, like full-screen webgl canvas, full-screen browsing and so.