- From: pes via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jan 2021 01:16:55 +0000
- To: public-webrtc-logs@w3.org
Thanks @alvestrand and @youennf ! Thank you for the clarification. I didn't quite have the correct understanding on my first read then. I have a broader question about the motivation behind the current approach, but want to make sure I 100% understand it first. Can you let me know what would should happen in each of the following cases? 1. I setSinkId with the deviceId of a valid audiooutput device, but one that hasn't been exposed to the page yet (Im thinking about the future, improving the privacy of enumerateDevices() changes we discussed previously)? Im trying to tease apart whether its "if enumerateDevices() is giving information about audiooutput devices, then you can bypass selectAudioOutput()", or if its "if has given access to the specific deviceId before on this page, you can bypass selectAudioOutput()", or a third thing? 2. the flows described in b seem to rely on deviceIds not being guessable. What happens if I manage to guess a deviceId, but which I haven't gone through the enumerateDevices requirements to have it revealed (either current or the additional, future discussed ones)? -- GitHub Notification of comment by pes10k Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/116#issuecomment-755013367 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 January 2021 01:16:56 UTC