- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Nov 2019 15:02:30 +0000
- To: public-webrtc-logs@w3.org
This PR removes an arguably redundant permission, which I approve of. But it still says user agents may revoke this ability (permission) _whenever they want_. This could be: 1. Never 2. During actual camera or mic capture, sabotaging post-gum in-content selection I think we need to define this in more detail to protect web interop. Original intent: when users revoke both camera and microphone permission, they revoke device-info as well (not before). I.e. ``` device_info = camera_permission || microphone_permission ``` This is true in all browsers I tested, so it must have been the original intent. Other parts like `groupId` support this notion. I vote we tighten the spec to conform with implementations here. This was also meant to be extensible, which is where I share @alvestrand's concern. E.g. ``` device_info = camera_permission || microphone_permission || speakers ``` If we end up not needing this because of https://github.com/w3c/mediacapture-output/pull/86, great! But it would still be nice if this spec didn't forbid extension, I thinkâForbidding user agents from doing whatever they want is not the same as forbidding other specs from extending things. Is there a way to write it like this? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/641#issuecomment-556041625 using your GitHub account
Received on Wednesday, 20 November 2019 15:02:31 UTC