[webrtc-pc] Does a PC depend on the page context? (#2516)

alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== Does a PC depend on the page context? ==
In a recent bug, we discovered that code in RTCPeerConnection depended on having a valid execution context.
This is no longer true if, for instance, the RTCPeerConnection's "window" is an iframe that has been destroyed - but references to the RTCPeerConnection may survive the iframe it was created in.
Apparently, some objects work fine without an execution context; some others don't. So it's up to the specification to say whether or not they are context dependent, and what happens if the context dies.

Alternatives I see (spec-wise):
- 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 the execution context dies, the RTCPeerConnection remains active and usable.

This may be related to the question in #2513 (another lifecycle issue).




Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2516 using your GitHub account