Closed Bug 1520332 Opened 7 years ago Closed 7 years ago

Screensaver not disabled on Hangouts call

Categories

(Core :: WebRTC: Audio/Video, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1434601

People

(Reporter: cpearce, Unassigned)

Details

I just had a hangouts call with an interview candidate, and the screensaver kicked in multiple times. Windows 10 x64, Nightly 2019-01-14.

Nils, do you know if we've changed something recently about this?

Flags: needinfo?(drno)

:jib, from the standup it sounded like you had some insight into this problem?

Flags: needinfo?(jib)

Yes, Chris showed me this code, which suggests both audio and video need to be present on a video element for the wakelock to take [1]:

bool HTMLVideoElement::ShouldCreateVideoWakeLock() const {
  // Make sure we only request wake lock for video with audio track, because
  // video without audio track is often used as background image which seems no
  // need to hold a wakelock.
  return HasVideo() && HasAudio();
}

From experimenting with web console during a Hangouts call, I inspected the main video element (of the peer, not self view) to learn its class name ("Gv1mTb-aTv5jf" in my case), and found it does not appear to have audio:

  » document.getElementsByClassName("Gv1mTb-aTv5jf")[0].srcObject.getAudioTracks().length
    0

[1] https://searchfox.org/mozilla-central/rev/dac799c9f4e9f5f05c1071cba94f2522aa31f7eb/dom/html/HTMLVideoElement.cpp#286

Flags: needinfo?(jib)

The same problem happens with Google Meet. Their team is looking into it.

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(drno)
You need to log in before you can comment on or make changes to this bug.