Open Bug 1908896 Opened 1 year ago Updated 3 days ago

meet.google.com - Output audio devices enumeration is not happening

Categories

(Web Compatibility :: Site Reports, defect, P2)

Product:
Web Compatibility
Component:
Site Reports
Platform:
Desktop
Windows 10
Type:
defect

Tracking

(Webcompat Priority:P2, Webcompat Score:6, firefox128 affected, firefox141 affected, firefox142 affected, firefox143 affected, firefox146 affected, firefox147 affected, firefox148 affected, firefox149 affected)

Project Flags:
Webcompat Priority P2
Webcompat Score 6
Tracking Flags:
Tracking Status
firefox128 --- affected
firefox141 --- affected
firefox142 --- affected
firefox143 --- affected
firefox146 --- affected
firefox147 --- affected
firefox148 --- affected
firefox149 --- affected

People

(Reporter: rbucata, Unassigned, NeedInfo)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: webcompat:contact-ready, webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs][webcompat:sightline][webcompat:japan])

User Story

platform:windows,mac,linux
impact:feature-broken
configuration:general
affects:all
branch:release
diagnosis-team:video-conferencing
user-impact-score:450

Environment:
Operating system: Windows 10
Firefox version: Firefox 128.0

Preconditions:
Audio speakers as an output source

Steps to reproduce:

  1. Access to https://meet.google.com/
  2. Create a meeting, or access to an already existing meeting.
  3. Go to speaker dropdown and observe

Expected Behavior:
Dropdown is listing output audio devices

Actual Behavior:
Only "System Default Speaker Device" appears

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in Firefox Release
  • Does not reproduce in Firefox Nightly, and Chrome

Created from https://github.com/webcompat/web-bugs/issues/139336

status-firefox128: --- → affected
Flags: needinfo?(dschubert)

Hi @dennis, I'm the reporter of the issue. May I help you with some info you need on the steps to reproduce?

Seeing this in Zoom (app.zoom.us) as well.

I'm suffering from the same problem as well.

This bug is similar to https://github.com/webcompat/web-bugs/issues/69160 .
When I check the settings of google meet from Firefox, I can see the dropdown menu for the microphone, but the speaker is always on the System Default Speaker Device, which is the first item on the menu. I cannot see any other speakers (like the Jabra Evolve Speaker of my headphones).

My Firefox is 131.0.3 (64-bit) and I'm running Tuxedo OS.

Tom, is this related/similar to the Voice intervention?

Flags: needinfo?(dschubert) → needinfo?(twisniewski)

No, the Google Voice intervention targets 132 changes (no longer leaks cameras and microphone info). This bug predates that (Firefox never leaked speaker info).

Meet is punting on speaker selection in Firefox here, which would require calling a separate API or living with only a subset of speakers listed. See https://blog.mozilla.org/webrtc/how-webrtc-speaker-selection-works/

Flags: needinfo?(twisniewski)
Severity: -- → S3
User Story: (updated)
Keywords: webcompat:contact-ready, webcompat:site-report
Priority: -- → P2
User Story: (updated)
Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs][webcompat:sightline]

I have the same issue with Google Meet on Windows 11 and Firefox 134.0.1. For me it does reproduce on Nightly (136.0a1). Chrome is fine. Workaround is that I can set Firefox to use my headphones as the default output device, but then all output from Firefox (YouTube, Spotify, everything else) only goes through my videoconferencing headphones.

Webcompat Priority: --- → P2
Webcompat Score: --- → 6
User Story: (updated)

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

status-firefox142: --- → affected

Any chance we can get action from Meet on this?

Flags: needinfo?(jmathies)
Whiteboard: [webcompat-source:web-bugs][webcompat:sightline] → [webcompat-source:web-bugs][webcompat:sightline][webcompat:japan]
Blocks: meet, webrtc-triage
Flags: needinfo?(jmathies)
Depends on: 1879204
User Story: (updated)

This is still an issue for me.

User Story: (updated)

We've done what we can. The rest is up to Meet.

Is this still an issue on Zoom (app.zoom.us)? Another user reported this as well.
If this issue still persist but it should be solved by meet (which is Google, remember) I think they might not be really interested on doing it and keep it as something their browser is doing better than FF.

No longer blocks: webrtc-triage

This is still an issue for me on the latest Nightly.

status-firefox146: --- → affected

Jim, can we coordinate with Meet here?

Flags: needinfo?(jmathies)

This is still an issue for me on the latest Nightly.

You need to log in before you can comment on or make changes to this bug.