Hi there,
We have noticed that when using the speech to text button in Microsoft Edge (both on our application and the Radzen components page) that it seems to be very temperamental and often turns itself off after 2/3 seconds without recording any of the audio as text - even if we continue talking. It seems to work fine on Google Chrome and occasionally also works on Edge, but not every time. Has anybody else noticed this as an issue?
This is a limitation of Microsoft Edge rather than of the component. RadzenSpeechToTextButton uses the browser's built-in Web Speech API — Chrome backs it with Google's speech service, while Edge backs it with Azure Speech Services, which is known to end recognition sessions on its own after a few seconds of silence even when continuous mode is requested. That's why the same code works reliably in Chrome but is temperamental in Edge, including on our demo site. Restarting the recognition session when the browser ends it prematurely is the common workaround for Edge.
UPDATE: We've pushed a fix: RadzenSpeechToTextButton now automatically restarts the recognition session when the browser ends it prematurely, so dictation keeps running until you actually click stop. The fix will be included in the next release later the week.
That’s amazing, thanks so much!