W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2012

Re: CHANGE: Re: [Bug 18485] New: Change DTMF API to be on PeerConnection

From: Harald Alvestrand <harald@alvestrand.no>
Date: Fri, 10 Aug 2012 18:58:13 +0200
Message-ID: <50253DA5.7060201@alvestrand.no>
To: public-webrtc@w3.org
On 08/10/2012 05:52 PM, Martin Thomson wrote:
> On 10 August 2012 00:12, Harald Alvestrand <harald@alvestrand.no> wrote:
>> I assume some responders won't support 4733. So even if all browsers support
>> it, canSendDTMF isn't guaranteed to be true always.
> Or, as you would have it, canSendDTMF isn't guaranteed to be true even
> if it was true in the past.  That bothers me a little.
Renegotiation is theoretically able to add or drop support for 4733 at 
any time, so that is trivially true.

We could have canSendDTMF return "don't know" rather than true or false 
when negotiation isn't done yet. I don't know if that adds value; people 
have quoted the use case for canSendDTMF as "hide the keypad when 
canSendDTMF is false"; I'm not sure what is useful here.
Received on Friday, 10 August 2012 16:58:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:32 UTC