- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Mar 2011 05:54:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12313
Summary: 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 t
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#dom
-peerconnection-close
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: other Hixie drafts (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org
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
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 16 March 2011 05:54:02 UTC