Open Bug 1835385 Opened 1 years ago Updated 1 year ago

Sites relying on HTMLMediaElement.setSinkId()

Categories

(Web Compatibility :: Knowledge Base, defect)

defect

Tracking

(Not tracked)

REOPENED

People

(Reporter: ksenia, Unassigned)

References

Details

User Story

url:inventaire.io/*
url:edu.meet.garr.it/*
url:meet.jit.si/*
url:voice.google.com/*
url:meet.google.com/*
url:web.skype.com/*

Symptoms:

  • Can't switch audio output device in a video call
  • Audio output selector missing when joining a conference
  • Navigator.mediaDevices.enumerateDevices() does not return output devices

Additional notes:

  • setSinkId is currently behind a "media.setsinkid.enabled" pref
Status: NEW → RESOLVED
Closed: 1 year ago
User Story: (updated)
No longer depends on: 1498512
Duplicate of bug: 1498512
Resolution: --- → DUPLICATE

Hey Andreas - please don't close this bug. :) The bugs inside the WebCompat::Knowledge Base are used by us to track real-world impact of known core issues. There's tooling on top of this, and we need this bug to stay open for as long as the core issue exists. We use dedicated bugs instead of the core bugs themselves just so that we can change those bugs as we want, without causing noise for the platform engineers.

I've reworded the title so that it's clearer. We'll also properly announce what this is all about once we've made more progress, so that this is less confusing!

Status: RESOLVED → REOPENED
Depends on: 1498512
No longer duplicate of bug: 1498512
Resolution: DUPLICATE → ---
Summary: Enable setSinkId pref by default → Sites relying on HTMLMediaElement.setSinkId()

and we need this bug to stay open for as long as the core issue exists

Oh, and that was poor wording. Even after a core bug is fixed, we will re-investigate known breakage, and then close it once we're certain that all the issues are fixed (or are certain that the issues have been re-diagnosed properly). Unfortunately, the tooling that alerts us about landed fixes isn't done yet!

Gotcha, sorry. They looked like dupes!

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