- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Sat, 09 May 2020 20:23:35 +0000
- To: public-webrtc-logs@w3.org
At *nix, by default , Chromium _only_ provides access to `'Default'` audio device, even if labelled `'audiooutput'` the track will still be from microphone - not _Monitor of_ device - unless changed at the OS itself by the user - which AFAICT by testing and experimenting, is not possible to access from JavaScript at the browser via an established API, see https://bugs.chromium.org/p/chromium/issues/detail?id=1013881. Right now the specification is not clear at all re audio capture, thus, there is no language in the specification which can point to at an implementer issue which conveys unambiguous language; the implementer, if the issue is not closed, could simply point to MAY language, if at all, and let the issue sit. How can a user cite the current iteration of this specification as authority for audio capture when MAY is used? -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/140#issuecomment-626230718 using your GitHub account
Received on Saturday, 9 May 2020 20:23:37 UTC