This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As I proposed during the meeting, the plan is to describe "enqueue a task" as: if the pc is closed, throw InvalidStateError add a task to a queue when the pc is closed, flush the queue, firing all callbacks with CancelledError (or something like that)
The wording used is "queue a task", which is defined in HTML5, but the change is specific to PeerConnection task queueing. PR needs to be generated.
This needs to also clarify that there is a single queue for the peer connection.
https://github.com/w3c/webrtc-pc/pull/22 I've not overridden the meaning of "queue a task", which is needed to manage dispatch from other (conceptual) threads. I've invented a new phrase that identifies the special RTCPeerConnection task queue.
WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues Please subscribe to the issues you want to keep watching.