2 ms·
I'm not aware of the APIs in question and it sounds like this probably to prevent fingerprinting of a device... but why not simply return only the default devic
by 0xCMP 5y ago
I'm not aware of the APIs in question and it sounds like this probably to prevent fingerprinting of a device... but why not simply return only the default device when enumerated?
It inherently makes sense that all those apps would try to understand what devices were available and even allow switching between them. It's often required because that entire stack between the browser, os, and device is very unreliable even on something like macOS.
Yea it's on MS to test and fix their stuff, but FF is the one losing market share and honestly part it sounds like they make their apis more prone to misuse. At least in this case.
- jeroenhd 5y agoI don't know why this broke in the first place, all I know is that I had no sound and that the device selection menu was borked where other video calling webapps worked just fine. The enumerateDevices API has been in Firefox for years [1]. To be fair(ish) to Microsoft, I did spoof Chrome's user agent because Microsoft forced a "this website doesn't work with your browser" screen in Firefox. Perhaps the failing API was an unstable Chrome-only API that they assumed works because of the UA. The browser compatibility screen communicates that they definitely tested it, that they definitely knew about the problem, and that they just didn't want to fix it. I just dropped Teams as an option and sent everyone who wanted to video chat Jitsi links. That worked fine while I needed it. If a company chooses not to support me, then I will choose not to use that company if I can. [1] https://caniuse.com/?search=enumerateDevices https://caniuse.com/?search=enumerateDevices