Re: [webrtc-pc] Inconsistencies in description of RTCDTMFToneChangeEvent.tone

The intent of the toneChange event was that it would fire whenever the
 tone changed - that is, at the end of each tone, including the one 
that makes the tone buffer empty.
This would be used to do things like move the highlight on a virtual 
dialpad if you want a visual indication that the tones are playing, or
 syntesize a "beep" that the user can listen to (there's no automatic 
feedback to the user that tones are playing).

I think this is consistent with the current description - it always 
says "indicates the tone that has just begun playing" or equivalent, 
and listing "empty string" as a special case indicating end of buffer.

If it was fired only when the tone buffer was empty, there would be no
 use for the "tone" argument.



-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/1014#issuecomment-277933488 
using your GitHub account

Received on Tuesday, 7 February 2017 08:35:12 UTC