Forum Discussion
MissyQ
Microsoft
Dec 01, 2020Top Feedback Summary for December 1
Welcome back to the Top Feedback Summary, Insiders! We have a lot of quick updates coming at you this week after our small break, so let’s hop into it.
We’re marking several items as Addressed....
florianSB
Dec 02, 2020Brass Contributor
Yes, Edge Canary 89.0.720.0
HotCakeX
Dec 02, 2020MVP
You also need to turn off Starup boost edge://settings/system
it prevents Edge to take the newly added command lines into effect immediately as some parts of the Edge is still in the memory and not fully closed.
only after doing that did I see the "msSpeechRecognition" in "command-lines" in edge://version/
showing that it is indeed enabled
it prevents Edge to take the newly added command lines into effect immediately as some parts of the Edge is still in the memory and not fully closed.
only after doing that did I see the "msSpeechRecognition" in "command-lines" in edge://version/
showing that it is indeed enabled
- florianSBDec 02, 2020Brass Contributor
HotCakeX
The start-up optimization was never enabled for me. Several restarts did not change anything and in edge/flags 'msSpeechRecognition' never shows.The command-line flag is working partially, but the Web Speech API is buggy. It shows intermediate results but always ends with 'Network Error'. You can follow the ongoing (older) discussion here: Re: Web Speech API support ? - Page 2 - Microsoft Tech Community
It is working in Google search though. Maybe only certain configurations of the API are buggy.
[EDIT] Actually it seems the feature is enabled now even when I remove the command-line flag. 'msSpeechRecognition' is nowhere to be found though.
- HotCakeXDec 02, 2020MVP
For me trying to use voice search on Google I got "internet connection error". a fake error.
voice search on Bing works fineEdge display language and Windows locale is En-US
- florianSBDec 02, 2020Brass Contributor
HotCakeX Voice search on Bing always worked because it uses Microsoft Azure services and not Web Speech API. Google voice search started working at some point, I can't say really what changed but my own apps (that work fine in Chrome) have the 'Network' issue described in the topic I linked. I've reported this bug through the official channels a few weeks ago btw.