Switching to Azure from Webspeech or Whisper requires opening Azure dropdown, select a text box, pressing enter key, and do this a second time after the pop up goes away. The API name displayed in the navbar does not change after the first enter, neither does the apiStatus value in the store, which indicates it is likely a reducer or subscription bug, not a purely visual one.
After switching to Azure from Webspeech, the Webspeech button stops working in the menu. No dispatch call to change API is logged either. However, the button works if you switch to Azure from Whisper, then attempt to switch to Webspeech.
Switching to azure has been fixed, but switching back to Webspeech is still glitchy:
If an user switches to azure, then immediately clicks on the Webspeech button without closing the API menu, nothing happens
If an user switches to azure, closes and reopens the API menu, then clicks on the Webspeech button, the API will change but transcription will stop. The user must stop and then restart listening to resume transcription
Switching to Azure from Webspeech or Whisper requires opening Azure dropdown, select a text box, pressing enter key, and do this a second time after the pop up goes away. The API name displayed in the navbar does not change after the first enter, neither does the apiStatus value in the store, which indicates it is likely a reducer or subscription bug, not a purely visual one.
After switching to Azure from Webspeech, the Webspeech button stops working in the menu. No dispatch call to change API is logged either. However, the button works if you switch to Azure from Whisper, then attempt to switch to Webspeech.