W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2018

[webrtc-pc] DTMF should not send before connecting

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Mon, 19 Feb 2018 08:22:11 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-298191982-1519028529-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== DTMF should not send before connecting ==
Current language:
https://w3c.github.io/webrtc-pc/#dom-rtcdtmfsender-insertdtmf

4. If transceiver's [[CurrentDirection]] slot is recvonly or inactive, throw an InvalidStateError.

However, before negotiation is completed, we don't know if it will be possible to send, and therefore we shouldn't do so.

Suggested change:

4. If transceiver's [[CurrentDirection]] slot is not sendonly or sendrecv, throw an InvalidStateError.

This requires a change to the following WPT tests so that they establish a call before testing DTMF:

RTCDTMFSender-insertDTMF.https
RTCDTMFSender-ontonechange-long.https
RTCDTMFSender-ontonechange.https



Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1774 using your GitHub account
Received on Monday, 19 February 2018 08:22:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 19 February 2018 08:22:15 UTC