This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Errors on a DTMFSender need to be reported through an error event, say DTMFError. 1. Invalid DTMF values 2. Values of duration and interToneGap with out of range values.
Shouldn't those throw an exception? Those can be easily detected synchronously.
(In reply to Justin Uberti from comment #1) > Shouldn't those throw an exception? Those can be easily detected > synchronously. I agree that duration and interToneGap ranges can be detected and thrown as exceptions. But onerror seems still required for reporting error in case of inserting invalid DTMF values [1], Bug: 25837. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25837
It's not required - we could parse the string synchronously and return an error, which would be nicer than playing out some tones and then stopping with an error.
(In reply to Kiran from comment #0) > 1. Invalid DTMF values Updated insertDTMF() algorithm to ignore unrecognized characters. Proposed fix [1] > 2. Values of duration and interToneGap with out of range values. This was fixed in [2]. Closing this bug as WONTFIX. [1] https://github.com/fluffy/webrtc-w3c/commit/d58a8bcf7ac4998dea3f670ccd278ce1c0b6c89e [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25976