This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
...and add a constructor for it. That way it would be compatible with the rest of the web platform.
I propose to close this issue because there are user-agent and web-page implementations using the current SpeechRecognitionError. If there's no disagreement, I'll close this on November 6.
Closing this issue as described above.
Reopening this because it seems that this hasn't shipped using the unprefixed name SpeechRecognitionError anywhere, just webkitSpeechRecognitionError in Chrome. I've done an httparchive search for "SpeechRecognitionError" and found 640 results. I went through all of them and they're all things like http://cdn.adsafeprotected.com/sca.js and not real uses. Changing this and adding a constructor therefore seems very safe from a compat perspective.
Suggested errata: "Section 5.1 Rename SpeechRecognitionError to SpeechRecognitionErrorEvent"
https://github.com/w3c/speech-api/pull/23