W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2016

[webrtc-pc] offerToReceiveAudio/offerToReceiveVideo remain in implementations (likely needed for compat)

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Mon, 20 Jun 2016 11:30:52 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-161174380-1466422252-sysbot+gh@w3.org>
foolip has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== offerToReceiveAudio/offerToReceiveVideo remain in implementations 
(likely needed for compat) ==
These were removed from the spec in 
e0c1dbee2ea722f5742610ec3cf1838f946cafa1 when `RTCRtpTransceiver` was 
added.

In https://codereview.chromium.org/2064593003/ it became apparent that
 support remains in the callback-based createOffer, and people expect 
them to work with the promise-based createOffer as well.

It's in Gecko and WebKit as well:
https://github.com/mozilla/gecko-dev/blob/b3ee63f6aa2af5788181d7bc42cd639bef08d4d9/dom/webidl/RTCPeerConnection.webidl#L62
 (in `RTCOfferOptions`)
http://trac.webkit.org/browser/trunk/Source/WebCore/Modules/mediastream/RTCOfferAnswerOptions.cpp?rev=198492#L79
 (also in `RTCOfferOptions`)

Lacking a concrete plan to get this removed from implementations with 
minimal compat risk, adding this back to the spec would probably be 
best. Perhaps it can be defined in terms of `RTCRtpTransceiver`?

Also, what to do about `OfferToReceiveAudio` and `OfferToReceiveVideo`
 with a capital O?

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/709 using your GitHub account
Received on Monday, 20 June 2016 11:30:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:48 UTC