12313 2011-03-16 05:54:00 +0000 <video> if a PeerConnection receives a new stream, then has close() called on it before the addstream event fires, the remoteStreams will change between close() and the close event. We should avoid that, probably by checking the readiness state 2012-07-18 18:40:35 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#dom-peerconnection-close P3 normal Unsorted 1 contributor ian ian mike contributor oldest_to_newest 46741 0 contributor 2011-03-16 05:54:00 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#dom-peerconnection-close Comment: if a PeerConnection receives a new stream, then has close() called on it before the addstream event fires, the remoteStreams will change between close() and the close event. We should avoid that, probably by checking the readiness state in the event for the handling of adding (and removing) of streams. Posted from: 76.102.14.57 by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16