search

webcompat / web-bugs

A place to report bugs on websites.
https://webcompat.com
Mozilla Public License 2.0
747 stars 67 forks source link

edu.meet.garr.it - Output device drop-down section is not available #71420

Open dag7dev opened 3 years ago

dag7dev commented 3 years ago

URL: https://edu.meet.garr.it

Browser / Version: Firefox 88.0 Operating System: Windows 10 Tested Another Browser: Yes Chrome, it works

Problem type: Something else Description: output device isnt shown Steps to Reproduce: while in a call, click on settings gear > output device isnt shown, only the input one

Browser Configuration
  • None

From webcompat.com with ❤️

softvision-oana-arbuzov commented 3 years ago

Thanks for the report, I was able to reproduce the issue. image

Note: The issue is not reproducible on Chrome.

Tested with: Browser / Version: Firefox Nightly 90.0a1 (2021-04-22) Operating System: Windows 10 Pro

Moving to Needsdiagnosis for further investigation.

karlcow commented 3 years ago

so for me on macOs, I get the same layout with access to the same features in Safari Tech Preview than in Firefox. And it doesn't work at all in Edge Canary (chromium); it fails with:.

react-dom.production.min.js:209 TypeError: Cannot read property 'store' of null
    at k (connectAdvanced.js:249)
    at Zo (react-dom.production.min.js:153)
    at Bi (react-dom.production.min.js:175)
    at Fi (react-dom.production.min.js:175)
    at Ni (react-dom.production.min.js:174)
    at Ss (react-dom.production.min.js:268)
    at gc (react-dom.production.min.js:246)
    at hc (react-dom.production.min.js:246)
    at sc (react-dom.production.min.js:239)
    at rc (react-dom.production.min.js:230)
as @ react-dom.production.min.js:209

Ah! in their source code.

    /**
     * White listing browsers that support audio output device selection.
     * It is not yet fully implemented in Firefox.
     * See: https://bugzilla.mozilla.org/show_bug.cgi?id=1498512
     */
    audioOutputSupportedBrowsers :
    [
        'chrome',
        'opera'
    ],

It depends on SetSinkId but they rely on user agent sniffing instead of feature detection.

see there:

                { 'audioOutputSupportedBrowsers' in window.config &&
                    window.config.audioOutputSupportedBrowsers.includes(me.browser.name) &&
                    <FormControl className={classes.formControl}>

It's why Edge doesn't get it unfortunately. It's not too complicated.

const audio_test = document.createElement('audio');
if (audio_test.setSinkId) {
  console.log("yeah audio baby");
} else {
  console.log("no luck yet");
}
karlcow commented 3 years ago

@digitarald on the microsoft side, that might be interesting for you. With feature detection this could work right away.

webcompat-bot commented 3 years ago

Generate outreach template

dag7dev commented 3 years ago

@softvision-oana-arbuzov I no longer can reproduce this issue. Can we close this or are you still experiencing issues?

softvision-oana-arbuzov commented 3 years ago

I can still reproduce it on my side. image

Tested with: Browser / Version: Firefox Nightly 95.0a1 (2021-10-08) Operating System: Windows 10 Pro