- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Feb 2018 17:40:43 +0000
- To: public-webrtc-logs@w3.org
@eladalon1983 so a use-case of this would be to allow a webextension to enforce a policy on a peerconnection? Why would the peerconnection in the renderer process expose its internal id to its own JS? At the same time, the extension would probably not use the RTCPeerConnection object as an interface. See [here](https://hacks.mozilla.org/2015/09/controlling-webrtc-peerconnections-with-an-extension/) for the messy way we solved this in Firefox a while back. A general way to address a peerconnection may be useful but that doesn't imply exposing the ID to javascript in RTCPeerConnection. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1775#issuecomment-366761552 using your GitHub account
Received on Monday, 19 February 2018 17:50:48 UTC