Closed Bug 1634043 Opened 4 years ago Closed 4 years ago

macOS Screensaver Turns On During Google Meet Meeting

Categories

(Core :: WebRTC, defect)

Product:
Core
Component:
WebRTC
Version:
75 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1434601

People

(Reporter: patrick, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wfh])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.129 Safari/537.36

Steps to reproduce:

  1. Set MacOS (10.15.4) screensaver to start after 5 minutes
  2. Launch Firefox 75
  3. Start meeting at meet.google.com
  4. Start grant permissions to camera and mic
  5. Do not touch the keyboard or mouse (or provide any input) for 5+ minutes

Actual results:

The screensaver turns on.

Expected results:

The screensaver should NOT turn on. Same as when you watch a youtube video. Screensaver should not turn on during video playback.

This problem does not exist in Google Chrome. I.e. the macOS screensaver does not turn on when using Google Meet in Google Chrome.

Whiteboard: [wfh]

Spohl:

any thoughts on this?

Flags: needinfo?(spohl.mozilla.bugs)

I wonder if there is anything in place that is supposed to handle this yet. Sending over to WebRTC for a look. If not, I suggest that we split this bug in two parts. I could add a sleep manager utility class that handles this on a macOS specific level and WebRTC could tap into this. Does WebRTC prevent screensavers from activating on any other platform?

Component: Untriaged → WebRTC
Flags: needinfo?(spohl.mozilla.bugs)
Product: Firefox → Core

Jib can you please help me triage this one. I think it's a known issue and we already have a bug about it.

Flags: needinfo?(jib)

So it looks like this is a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1434601 but that bug should be reprioritized due to work from home?

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.