Forum Discussion
Top Feedback Summary for December 1
because when I try the same thing on Edge stable 87, i get an error on the console after allowing the mic access.
HotCakeX You should see that the mic is enabled by the animated red dot next to the browser tab and if you start speaking you should see results popping up in the dev console ... or error messages 😉
I wouldn't be surprised if Google was tinkering with the page to make other browsers look bad, but in this case I really think its the Web Speech API implementation in Edge. I've been experimenting with it the last days and can confirm that it will occasionally drop the "onend" event and it will throw "network" error (critical) where it should throw "no-speech" (non-critical, can be ignored). Also the 'continuous' mode will constantly throw "network" errors as well.
I've reported all these bugs via the official channel and hope they will fix it before it arrives in the release ^^.
- Yup, exactly experiencing the same thing.
this could be an intentional move by Google, wouldn't be their first time. because web speech API works now in that demo above Yes, https://www.google.com/intl/en/chrome/demos/speech.html works, but not Google voice search at http://www.google.com.
When clicking on the webpage microphone at http://www.google.com after a second or two the message "No internet connection" replaces the Google search box. The browser tab does show the red recording dot and the microphone symbol appears in the address bar.
Instead I keep seeing that in console.
by the way I tried speech to text in here and it works
https://www.google.com/intl/en/chrome/demos/speech.html
