- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Sep 2018 04:46:43 +0000
- To: public-webrtc-logs@w3.org
It might be good to separate the issues: 1. navigator.mediaDevices.getUserMedia is not restricted to secure contexts in most browsers. It will usually reject the promise due to being called in an insecure context. It seems legitimate to update the spec according the current behavior. Ideally, we would mark it (or even better mediaDevices) as SecureContext. The compatibility risk probably needs to be assessed. 2. Is there a scenario where navigator.mediaDevices.enumerateDevices would usefully resolve in contexts where getUserMedia will not be available? 3. navigator.getDisplayMedia is probably currently aligned with navigator.mediaDevices.getUserMedia in terms of behavior. It would be nice to update the spec accordingly. The compatibility risk to move it to SecureContext is probably lower. 4. RTCPeerConnection is not restricted in shipping browsers AFAIK. I do not see a clear motivation to make such change at this point. For instance, RTCPeerConnection has some functional similarities to WebSocket which is not restricted either. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1945#issuecomment-420510604 using your GitHub account
Received on Wednesday, 12 September 2018 04:46:47 UTC