Top Feedback Summary for December 1

HotCakeX MikeDNZ 

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 ^^.

Yes, https://www.google.com/intl/en/chrome/demos/speech.html  works, but not Google voice search at www.google.com. 

When clicking on the webpage microphone at 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.

HotCakeX ok that looks weird, why does it keep logging "img"? ^^

Your result function looks exactly like this?

rec.onresult = console.log;

Anyway I think it works, its just logging the wrong stuff. Maybe an issue with this website. If the other demo works you should be good.

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

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 😉

HotCakeX Currently: Yes. Since I don't know exactly when it started working (I've tried it a couple of times with most recent Canary) I can't guarantee though that its reproducible ^^.

Something that should work on any HTTPS page (just open the Dev Tools and type it in) is this:

var rec = new window.webkitSpeechRecognition(); 
rec.onresult = console.log; 
rec.onerror = console.error;
rec.start();

I still have to find out which configuration option is messing it up for my app.

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.