Re: [mediacapture-main] What is the purpose of requiring a successful gUM call before enumerateDevices? (#1019)

> Invalid, as explained in https://github.com/web-platform-tests/interop/issues/849#issuecomment-2494785406.

Your statement is in conflict with custom logging added to Chromium, similar to the one below.

> I use MS teams in Firefox regularly

Well, here is what Teams does in the modified Chromium:
```
[6147:1:1204/073335.016084:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073337.533984:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073337.599033:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073337.617704:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073338.145701:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073338.372615:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073338.468623:ERROR:media_devices.cc(420)] ENUMERATE
[6147:1:1204/073338.902420:ERROR:user_media_request.cc(393)] GUM
```
I have asked folks to take a look because polling is not great which might yield a statement about why they do ED-before-GUM too.

> Said differently: For returning users, device pickers aren't populated. Why single out a pity-group? What you call "broken" is the behavior everyone else gets today.

That is a question for a product manager (in this case at Zoom), they are unlikely to respond in this venue.

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1019#issuecomment-2518287306 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 4 December 2024 18:55:57 UTC