Skip to content

api.SpeechRecognition - Edge does not actually support SpeechRecognition Web Speech API #22126

Open
Open
api.SpeechRecognition - Edge does not actually support SpeechRecognition Web Speech API#22126
Labels
browser:edgeIssue about Edge support that differs from Chrome.data:apiCompatibility data for Web API features. https://developer.mozilla.org/docs/Web/APIinfo neededMore information is needed before this can be reviewed or acted on.

Description

@mbforbes
mbforbes
opened on Jan 31, 2024

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/SpeechRecognition

What specific section or headline is this issue about?

Browser compatibility

What information was incorrect, unhelpful, or incomplete?

Microsoft Edge does not actually support the SpeechRecognition Web Speech API. It's listed that it is "Implemented with the vendor prefix: webkit." While using it does not generate any errors, the implementation does nothing. No results are ever returned.

This may be an issue of semantics. Does implementing with a no-op count as implementing? :-)

What did you expect to see?

The Edge column should either have a "No" or a warning sign because the implementation is broken.

Do you have any supporting links, references, or citations?

Two users have tested on two different devices, each on two separate pages (4 total tests). For all of them, Chrome's speech recognition works correctly, and Edge never returns any results.

n=4 isn't huge, but it's been consistent. I also believe this issue is known by Edge.

Here's an example test page this can be used to verify SpeechRecognition on the Web Speech API:
https://www.google.com/intl/en/chrome/demos/speech.html

Do you have anything more you want to share?

No response

MDN metadata

Page report details

Activity

  1. bsmth
    transferred this issue frommdn/contenton Feb 1, 2024

  2. bsmth commented on Feb 1, 2024

    @bsmth
    bsmth
    on Feb 1, 2024
    Member

    Hi @mbforbes thanks a lot for raising this. I've moved it over to the browser-compat-data repo which is where the source of this compatibility data is managed.

    Just to check, there are some demos to try to reproduce this. I did the following:

    git clone https://github.com/mdn/dom-examples.git
cd dom-examples/web-speech-api/speech-color-changer
http-server -c-1
# Available on:
#   http://127.0.0.1:8080

    This works on Chrome, but fails on Edge with "Language not supported" error. You may want to try the other examples in that repo, but that doesn't look promising to me.

    See https://github.com/mdn/dom-examples/blob/40cb0f10d859384a6160861ccbbf78f337fed6a0/web-speech-api/speech-color-changer/script.js#L17

  3. queengooborg
    added
    data:apiCompatibility data for Web API features. https://developer.mozilla.org/docs/Web/API
    on Feb 1, 2024

  4. mbforbes commented on Feb 1, 2024

    @mbforbes
    mbforbes
    on Feb 1, 2024
    Author

    Hey @bsmth thank you for the reply, and apologies for my newb raising of this issue in the wrong repo 😅 I appreciate you looking into it already!

  5. bsmth commented on Feb 8, 2024

    @bsmth
    bsmth
    on Feb 8, 2024
    Member

    Hey @bsmth thank you for the reply, and apologies for my newb raising of this issue in the wrong repo 😅 I appreciate you looking into it already!

    Not a problem, I hope the info helps investigate / narrow it down.

  6. gabrieljbaker commented on Feb 15, 2024

    @gabrieljbaker
    gabrieljbaker
    on Feb 15, 2024

    @mbforbes , I've been trying to get recognition to work in Edge for a while - definitely confirmed that it does not work. Wild that Safari has this and Edge doesn't.

  7. mbforbes commented on Feb 15, 2024

    @mbforbes
    mbforbes
    on Feb 15, 2024
    Author

    So, with a higher sample size, the plot has thickened. I have confirmed reports of Edge working for some folks. But for others, it doesn't work at all. Anecdotally, it's about 1:4 working vs not, but the n is too small. No idea when vs not.

  8. bsmth commented on Feb 22, 2024

    @bsmth
    bsmth
    on Feb 22, 2024
    Member

    So, with a higher sample size, the plot has thickened. I have confirmed reports of Edge working for some folks. But for others, it doesn't work at all. Anecdotally, it's about 1:4 working vs not, but the n is too small. No idea when vs not.

    For those that report it working, could you get some information on operating system and browser version? That would really help figure out what's happening here.

  9. gabrieljbaker commented on Mar 26, 2024

    @gabrieljbaker
    gabrieljbaker
    on Mar 26, 2024

    @bsmth and @mbforbes , here's some color to it:
    image

  10. mobilepadawan commented on Apr 26, 2024

    @mobilepadawan
    mobilepadawan
    on Apr 26, 2024

    Does anyone know if there is exists an estimated date to start supporting Edge on Mac OS over ARM processor?

    Chrome is working fine in this O.S. and processor.

  11. bsmth commented on May 2, 2024

    @bsmth
    bsmth
    on May 2, 2024
    Member

    here's some color to it

    Thanks for picking that up. Here's a link to the post in question for convenience: https://twitter.com/khmyznikov/status/1772573147755073667

    I think we could add a note for Edge entry that this depends on Azure Speech component & is not yet supported on ARM machines, it would be great to link to a bug tracker or some other official docs for this.

  12. caugner
    added a parent issue on Jan 21, 2025
  13. caugner
    changed the title [-]Edge does not actually support SpeechRecognition Web Speech API[/-] [+]api.SpeechRecognition - Edge does not actually support SpeechRecognition Web Speech API[/+] on May 7, 2025

  14. caugner commented on May 7, 2025

    @caugner
    caugner
    on May 7, 2025
    Contributor

    In March 2025, I looked into this issue while triaging mdn/dom-examples#301, and could confirm with this example that Web Speech API with speech recognition lang set to en-US failed in Edge 134 (and Brave) with the language-not-supported error.

    Using BrowserStack Live, I determined that all versions back to Edge 86 were affected, suggesting an issue with the backend service. (In Edge 85 and earlier I got a different error,no-speech, possibly as BrowserStack Live doesn't support microphone input.)

    Back then, I reported the issue through Edge (… > Help and feedback > Send feedback), and reached out to @captainbrosset, who confirmed a fix for release in the week of March 12th, presumably a Edge 134 dot release.

    Today, I just checked again, and could still reproduce the issue on macOS in Edge 135.0.3179.73, and (after updating) in Edge 136.0.3240.50. However, on Windows 11 (via BrowserStack Live), I can no longer reproduce the issue in Edge 91 to Edge 135 (only in Edge 86 to 90).

  15. caugner
    added
    info neededMore information is needed before this can be reviewed or acted on.
    on May 7, 2025

  16. sushraja-msft commented on May 21, 2025

    @sushraja-msft
    sushraja-msft
    on May 21, 2025

    @caugner - I am assuming this macOS machine is an ARM mac device? We have a bug in Edge for ARM devices where the component is not being delivered. Ill update when that is fixed.

  17. caugner commented on May 21, 2025

    @caugner
    caugner
    on May 21, 2025
    Contributor

    I am assuming this macOS machine is an ARM mac device?

    @sushraja-msft Good catch: I'm on a Macbook M1 Pro myself, and in BrowserStack Live, I can reproduce the issue in Edge 136 on macOS, but not in Edge 136 on Windows 11.

    Will this only be fixed in future versions, or will Edge 136 and older versions be also fixed retroactively?

  18. gabrieljbaker commented on Jul 8, 2025

    @gabrieljbaker
    gabrieljbaker
    on Jul 8, 2025

    any update on that @sushraja-msft ?

  19. sushraja-msft commented on Jul 8, 2025

    @sushraja-msft
    sushraja-msft
    on Jul 8, 2025

    We are working on a rewrite with better proxy and ARM support. I don't have an ETA yet, still in prototyping stages, but this is being worked on.

  20. mobilepadawan commented on Jul 8, 2025

    @mobilepadawan
    mobilepadawan
    on Jul 8, 2025

    My apologize if my next comment sounds like an ape.

    I have no knowledge at all about if there is exists a Chromium for MacOS (a blank branding of the blink engine) with this feature working on it. I suppose could be a good choice to take that functional part of this feature to accelerate the support on Edge.

    I teach advanced programming skills with JS in a tertiary school, and also I have in mind a couple of web projects where this feature could be a highlight.

    Every time I should teach Voice Recognition in JS I need to switch to Chrome.

  21. sushraja-msft commented on Jul 9, 2025

    @sushraja-msft
    sushraja-msft
    on Jul 9, 2025

    The implementation in Chromium uses Google's speech service. So, this is something other Chromium browsers have to re-implement unfortunately.

  22. caugner
    added
    browser:edgeIssue about Edge support that differs from Chrome.
    on Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    browser:edgeIssue about Edge support that differs from Chrome.data:apiCompatibility data for Web API features. https://developer.mozilla.org/docs/Web/APIinfo neededMore information is needed before this can be reviewed or acted on.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions