New issue
Advanced search Search tips

Issue 724992 link

Starred by 0 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Deal with null handler for RTCDataChannel in all cases

Project Member Reported by guidou@chromium.org, May 22 2017

Issue description

Bug 717912, bug 717872 and probably bug 718364 are caused by assuming that the RTCDataChannel handler is never null.

This assumption is incorrect, and crrev.com/2888043003 fixes it for close and send, which are the methods directly causing the bugs.

A solution must be found for other methods that assume they are never called with a null handler (and are currently not causing problems) and which return values to the caller.

A possible solution is to throw a JavaScript exception, but the spec compliance of this solution needs to be assessed.


 

Comment 1 by guidou@chromium.org, May 22 2017

Labels: -Pri-3 Pri-2

Comment 2 by guidou@chromium.org, May 22 2017

Labels: OS-All
Components: Blink>WebRTC>PeerConnection

Sign in to add a comment