Bugzilla

Spec says we should queue a single task that: 
1. fires the RTCPeerConnection.datachannel event, and 
2. queues a task that fires the RTCDataChannel.open event.

Instead, we queue two separate tasks for these things from STS, like so:
Task 1. Fires the RTCPeerConnection.datachannel event, and 
Task 2. Fires the RTCDataChannel.open event.

This can result in the open event firing early, or late, depending on the lag between scheduling these two tasks.

This bug appears to be causing an intermittent failure over in bug 1591199.

Spec says we should queue a single task that: 
1. fires the RTCPeerConnection.datachannel event, and 
2. queues a task that fires the RTCDataChannel.open event.

Instead, we queue two separate tasks for these things from STS, like so:
Task 1. Fires the RTCPeerConnection.datachannel event, and 
Task 2. Fires the RTCDataChannel.open event.

This can result in the open event firing early, or late, depending on the lag between scheduling these two tasks.

This bug appears to be causing an intermittent failure over in bug 1591199, which looks the same as a fission-only intermittent failure we see already.