Bugzilla

(In reply to Gabriele Svelto [:gsvelto] from comment #9)
> YFortunately fixing it should be trivial.

Well, that's good to hear. :)

From a preliminary scan of the wake lock and process priority manager code, it looks like we set the wake locks for audio and video in the _content process_, and map that to the window which requested the wake lock.

I see us going pretty deep into Hal once we register that wake lock, but I don't see anything sending a message up to the parent to actually put the lock in up there (presumably, the parent needs to know about the wake locks for them to have any effect).

Is that plumbing just missing? Or am I not seeing it?

(In reply to Gabriele Svelto [:gsvelto] from comment #9)
> Fortunately fixing it should be trivial.

Well, that's good to hear. :)

From a preliminary scan of the wake lock and process priority manager code, it looks like we set the wake locks for audio and video in the _content process_, and map that to the window which requested the wake lock.

I see us going pretty deep into Hal once we register that wake lock, but I don't see anything sending a message up to the parent to actually put the lock in up there (presumably, the parent needs to know about the wake locks for them to have any effect).

Is that plumbing just missing? Or am I not seeing it?