- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Apr 2020 12:04:22 +0000
- To: public-webrtc-logs@w3.org
> * When the execution context dies, the RTCPeerConnection is closed, a "signalingStateChange" event is fired at it, and no further operation on it is possible. When context dies, we probably do not want to fire an event. > * When the execution context dies, the RTCPeerConnection remains active and usable. There is obviously a time where the peer connection would need to go away so I am not sure we want that either. It would be interesting to test the existing behavior in current implementations. I would think that Safari is basically neutering the RTCPeerConnection, as if close() was called. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2516#issuecomment-618362995 using your GitHub account
Received on Thursday, 23 April 2020 12:04:24 UTC