New issue
Advanced search Search tips

Issue 740323 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 777617
Owner:
Closed: Sep 4
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Feature

Blocked on:
issue webrtc:7600



Sign in to add a comment

Implement RTCPeerConnection.prototype.addTransceiver

Project Member Reported by phistuck@gmail.com, Jul 8 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
Implement RTCPeerConnection.prototype.addTransceiver.

What is the expected behavior?

What went wrong?
Not implemented.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

WebKit advocates addTransceiver as well now in their recently revealed implementation.
https://webkit.org/blog/7763/a-closer-look-into-webrtc/

I see that no other browser implemented this API (except the upcoming Safari 11) -
https://developer.microsoft.com/en-us/microsoft-edge/platform/catalog/?page=1&q=addTransceiver

Any (short or long) plans to implement this in Chromium?
 
Labels: Needs-Feedback
@phistuck: Thanks for filing the issue.

Could you please provide us a sample URL to implement the WebRTC call?

Thanks!1
Components: -Blink>WebRTC Blink>WebRTC>PeerConnection
Labels: -Needs-Feedback -Arch-x86_64 OS-Android OS-Chrome OS-Fuchsia OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)

Comment 3 by guidou@chromium.org, Jul 31 2017

Labels: -Type-Bug Type-Feature
Owner: hbos@chromium.org
Status: Assigned (was: Untriaged)

Comment 4 by hbos@chromium.org, Aug 14 2017

Blockedon: webrtc:7600
Mergedinto: 777617
Status: Duplicate (was: Assigned)
This is an old bug fixed by the addition of transceviers.

Sign in to add a comment