New issue
Advanced search Search tips

Issue 701572 link

Starred by 1 user
Status: Assigned
Owner:
hbos@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 673698



Sign in to add a comment

RTCPeerConnection#setLocalDescription argument filureCallback should not be optional

Project Member Reported by lunalu@chromium.org, Mar 14 2017 
According to the spec, this argument should not be optional

Comment 1 by guidou@chromium.org, Mar 16 2017

Owner: guidou@chromium.org
Status: Assigned (was: Untriaged)

Comment 2 by guidou@chromium.org, Mar 14 2018

Owner: hbos@chromium.org

Comment 3 by hbos@chromium.org, Mar 14 2018 

This is a legacy API, only in the spec because it is listed in the "legacy section". Probably the right action is update the spec to reflect the legacy API rather than break existing usage of the legacy API not using the failure callback.

chromium-side this is WontFix, but I'll leave this bug open as a reminder to update the spec when time allows (P-3)
►

Sign in to add a comment