This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12313 - <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
Summary: <video> if a PeerConnection receives a new stream, then has close() called on...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-16 05:54 UTC by contributor
Modified: 2012-07-18 18:40 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2011-03-16 05:54:00 UTC 
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