Forum Discussion

MissyQ's avatar
MissyQ
Former Employee
Dec 01, 2020

Top 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's avatar
florianSB
Copper Contributor
Dec 02, 2020

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.

HotCakeX's avatar
HotCakeX
MVP
Dec 02, 2020

For me trying to use voice search on Google I got "internet connection error". a fake error.
voice search on Bing works fine

Edge display language and Windows locale is En-US

  • florianSB's avatar
    florianSB
    Copper Contributor
    Dec 07, 2020

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

  • HotCakeX's avatar
    HotCakeX
    MVP
    Dec 04, 2020
    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
  • MikeDNZ's avatar
    MikeDNZ
    Copper Contributor
    Dec 04, 2020

    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.

     

     

  • florianSB's avatar
    florianSB
    Copper Contributor
    Dec 02, 2020

    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.

  • florianSB's avatar
    florianSB
    Copper Contributor
    Dec 02, 2020

    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's avatar
    HotCakeX
    MVP
    Dec 02, 2020
    I just tried it on this website, Edge asked me to use mic and i enabled it, nothing happened after, does it mean it's working? 🙂
    because when I try the same thing on Edge stable 87, i get an error on the console after allowing the mic access.
  • florianSB's avatar
    florianSB
    Copper Contributor
    Dec 02, 2020

    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's avatar
    HotCakeX
    MVP
    Dec 02, 2020
    Oh okay so while it's still not working for me, you can use voice search on Google without any speech flags or command lines, right?
  • florianSB's avatar
    florianSB
    Copper Contributor
    Dec 02, 2020

    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.

Resources