Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Speech API Down #301

Closed
ToddTaylor opened this issue Mar 10, 2025 · 2 comments
Closed

Web Speech API Down #301

ToddTaylor opened this issue Mar 10, 2025 · 2 comments
Labels
needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.

Comments

@ToddTaylor
Copy link

What information was incorrect, unhelpful, or incomplete?

In my own custom developer speech-to-text web application, I've been receiving a "network" exception for several days. I'm seeing the same issue when attempting to use the Speech Color Changer demo, thus eliminating my code as being the cause of the issue. The web developer console does not show any error messages, like because the web app script is catching the exception.

Using Telerik's Fiddler, it appears as though a call is being made to a Google speech API "under the covers" and it is returning a 400 response:

https://www.google.com/speech-api/full-duplex/v1/down?key=qztbjzBqJueQZLFkwTTJrieu8Vw3789u&pair=CD1CBA47B337E03C&output=pb

Because the above URL is returning a 400, does this mean that browser speech-to-text recognition is dead? If not, is there a URL I can go to see the status of the service? I don't see how anyone can use this feature when it's so unstable.

Browser(s): Full patched / updated Brave and Microsoft Edge

https://mdn.github.io/dom-examples/web-speech-api/speech-color-changer/

Image

What did you expect to see?

The Speech Color Changer app should not being reporting a "network" error, but instead should convert incoming speech to a color.

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

https://mdn.github.io/dom-examples/web-speech-api/speech-color-changer/

Do you have anything more you want to share?

No response

@ToddTaylor ToddTaylor added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Mar 10, 2025
@caugner
Copy link
Contributor

caugner commented Mar 12, 2025

Hi @ToddTaylor, I just tried this dom-example in Chrome 134 on macOS, and it worked without issues.

However, I can reproduce issues in Brave 1.76.74 (Chromium 134) and Edge 134:

  • Brave shows Error occurred in recognition: network
  • Edge shows Error occurred in recognition: language-not-supported

The Brave limitation seems to be a known issue: brave/brave-browser#2802

Edit: As for Edge, I have reported the issue via "Help and Feedback" > "Send feedback", and reached out to the Edge team, so they will look into it.

@caugner
Copy link
Contributor

caugner commented Mar 12, 2025

As this seems to be a compatibility issue, and there is nothing wrong with the example itself, I'm going ahead and close this issue as won't fix.

@caugner caugner closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened.
Projects
None yet
Development

No branches or pull requests

2 participants