- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Jul 2020 01:34:01 +0000
- To: public-webrtc-logs@w3.org
> We have considered adding a speaker-only permission for setSinkId (to better support the non-communications cases that don't require a mic), but there has been little demand for it and an there have been concerns that an UI prompt just for speakers might be confusing to users since the default speaker does not require authorization. "demand" for "it" (where it is capturing audio output to speakers, headphones, "What-U-Hear", and "demand" is are feature requests) - https://github.com/w3c/mediacapture-main/issues/629 - https://github.com/w3c/mediacapture-main/issues/650 - https://github.com/w3c/mediacapture-main/issues/654 - https://github.com/w3c/mediacapture-screen-share/issues/140 Chromium issues - https://bugs.chromium.org/p/chromium/issues/detail?id=1013881 - https://bugs.chromium.org/p/chromium/issues/detail?id=1032815 Firefox and Nightly implementation of `getUserMedia()` prompt, which lists `Monior of <device>` at Linux is not confusing. Chromium implementation just asks for microphone permission, confusion at Chromium can arise because the user does not select any particular device and `enumerateDevices()` does not list the correct device if or when the default microphone is changed by the user. - https://github.com/w3c/mediacapture-main/issues/693 From the results of various experiments and tests it is currently impossible to capture speaker output at Chromium within the confines of the implementation of `getUserMedia()`. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/91#issuecomment-659103814 using your GitHub account
Received on Thursday, 16 July 2020 01:34:04 UTC