01-13-2020 03:55 AM
01-13-2020 03:55 AM
Currently Edge (81.0.381.0) is behaving strange when using the Web Speech API for speech recognition. The interface exists, but does not work AND does not throw any error.
Here is a quick code example:
var rec = new window.webkitSpeechRecognition(); rec.onresult = console.log; rec.onerror = console.error; rec.start();
Are there any plans to either:
a) Fully implement the speech recognition part or ...
b) ... throw proper errors?
Since Microsoft is already using speech recognition in Windows, has the technology for offline and online ASR and has the cloud architecture it should be no big deal to fully support it right?
It would be really great to finally get a 2nd browser that actually has a working implementation of the API (Google is doing it for 6 years now since Chrome 33).
02-10-2020 03:45 PM
@florianSB Thanks for reaching out and letting us know. I'll pass this along to our Accessibility Team (unless you've noticed a change since originally posting this) and will let you know if/when they have any additional thoughts.
Project & Community Manager - Microsoft Edge
02-12-2020 02:45 PMSolution
@florianSB thanks for reporting this issue. We are aware of this and are working to wire up Speech recognition in the upcoming future versions of Edge for our customers. Once this feature is out in Canary, I will let you know so you can try it out.
04-18-2020 04:13 AM
This is still not working on Edge Canary 84.0.488.0
The Speech Recognition starts (onspeechstart event) but no response is received (onresult event).
07-24-2020 03:04 PM
@__Isaac After checking-in with the team, I'm happy to confirm that this is still in the works! It sounds like there were some unexpected technical roadblocks, but they are still moving forward.
Program Manager & Community Manager - Microsoft Edge
07-27-2020 01:10 AM
Good to hear :)
It would still be good to throw at least a proper error message until the actual speech recognition is connected. I don't want to return to the old days where I need to check the navigator user-agent before I can use the API properly :\
Currently Edge still pretends to do something instead of failing gracefully.