RTCPeerConnection.getConfiguration |
||||||||||||
Issue descriptionFeature description: Support the getConfiguration call as specified. Eng owner: zhihuang@chromium.org WebRTC spec: http://w3c.github.io/webrtc-pc/#widl-RTCPeerConnection-getConfiguration-RTCConfiguration Split off from https://bugs.chromium.org/p/chromium/issues/detail?id=587453, which used to cover both the "set" and "get" methods, but "set" ended up shipping first.
,
Apr 24 2017
Bumping to M60. Please correct if that's wrong.
,
May 25 2017
Bumping again, to M61. guidou@ or hbos@, would you be able to take this over? The CL (https://codereview.chromium.org/2706563003/) is almost ready to land, it's just been in limbo because other priorities came up for us. I think the only thing left to do is add tests for the normalization of "iceServers".
,
May 30 2017
I can take this on in-between RTCRtpSender work.
,
May 30 2017
,
Aug 14 2017
Changing milestone to M62. Please correct of that's wrong.
,
Jan 30 2018
,
Aug 1
,
Aug 15
https://www.google.com/url?q=http://web-confluence.appspot.com/%23!/catalog?releases%3D%255B%2522Safari_11.1_OSX_10.13.4%2522,%2522Edge_17.17134_Windows_10.0%2522,%2522Firefox_61.0_Windows_10.0%2522,%2522Chrome_68.0.3440.75_Windows_10.0%2522%255D%26q%3D%2522RTCPeerConnection%2523getConfiguration%2522&sa=D&source=hangouts&ust=1534417729024000&usg=AFQjCNEaLHNG0EoLu7Atjnej5C3Rn_wzXQ shows that this API is now supported in the three other major browsers, one of only two such APIs where Chrome is the last to ship. hbos@, is this in the planning still?
,
Aug 15
,
Aug 21
,
Aug 21
Yay! |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by deadbeef@chromium.org
, Mar 23 2017