-
Notifications
You must be signed in to change notification settings - Fork 53
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
Network Error with webkitSpeechRecognition on Updated Microsoft Edge #320
Comments
I have the same issue in Edge of the webkitSpeechRecognition API returning a network error after Edge updated to version 134.0.3124.51. Everyone that uses an extension or a website that uses the webkitSpeechRecognition has the same issue. Previous to this webkitSpeechRecognition has been working in Edge for 3 years. |
Same problem, while using speech API !!!!!!!!!!!!!!! |
Edition Windows 11 Pro Same issue. |
Thanks for the report, this is being fixed in the next patch update to edge stable releasing this week. |
Not related to DevTools |
Description:
After updating Microsoft Edge to the latest version (Version 134.0.3124.51 (Official build) (64-bit)),
My speech recognition project now encounters a "Network error" when using the webkitSpeechRecognition API. This issue did not occur with previous versions, where the speech recognition functioned correctly.
Steps to Reproduce:
Update Microsoft Edge to the current version (Version 134.0.3124.51 (Official build) (64-bit)).
Launch the speech recognition project that utilizes webkitSpeechRecognition.
Initiate voice input.
Observe the "Network error" message.
Expected Behavior:
The speech recognition should work as it did prior to the update, without throwing any network-related errors.
Actual Behavior:
A "Network error" is triggered immediately when attempting to use speech input, which interrupts the intended functionality.
Additional Context:
The project was running without issues before the Edge update.
No changes were made to the implementation of webkitSpeechRecognition.
Please investigate and advise on potential fixes or workarounds.
The text was updated successfully, but these errors were encountered: