Forum Discussion
florianSB
Jan 13, 2020Brass Contributor
Web Speech API support ?
Currently Edge (81.0.381.0) is behaving strange when using the https://developer.mozilla.org/en-US/docs/Web/API/SpeechRecognition for speech recognition. The interface exists, but does not work AND d...
Poodll_Guy
Jun 01, 2021Copper Contributor
Well I'd rather say they forgot to disable the API when they switched to the Chromium based Edge 😉
This is correct. It is also the case with Brave browser, which behaves identically. I had not realised Safari Web Speech API was now working. That is very good news. Thanks for sharing,
florianSB
Jun 07, 2021Brass Contributor
I've just tested the Web Speech API in the current release of (normal, no-flags, non-dev, non-canary) version of Edge again ... and it seems to work well now :-). I'm cautiously optimistic that we have actually 3 browsers now (Chrome, Edge, Safari) with full support ^^. Took them only 9 years 😛
- StephaneDezMay 12, 2022Copper Contributor
Hy mikohead
did you find a solution about the freeze ? I have the same issue 😕
it seems that it came from the onError event but i'm not sure.Regards
- dtylesJul 24, 2021Copper ContributorflorianSB
I tried your test application the day after your post and it indeed worked but the following day it stopped working (same as my own tests) producing "Error: 'E0? - network'". In Edge release notes I see that Microsoft says that support for speech recognition is added for google.com and similar web sites. I wonder if speech recognition worked for all web sites for couple days (as an oversight) and then was shutdown? Would be good to understand what Microsoft's intentions are here. - florianSBJun 09, 2021Brass ContributorIt seems to work fine for me. You can test it here: https://sepia-framework.github.io/app/index.html
(simply skip the login to get to demo mode and press the microphone below). Its an older version of my app that wasn't working for a while in Edge because of all the initial quirks in Edge's Web Speech API but it has fixed itself recently and now works almost with the same performance as in Chrome ^^.