You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.
The "Doorhanger" displays the "Sorry, there was an issue" text after around 4 seconds and type input is not visible anymore.
Notes:
Reproduced on Mac 10.14.6 and Win10x64 with Firefox Nightly 71.0a1 (64-bit).
The written command can be continued and results will be shown after pressing "Enter" in both the "Doorhanger" and in new opened tabs, but the continuation of the command will not be visible when it's written.
Sometimes the "Sorry, there was an issue" text is displayed after around 8 seconds after the written command was started.
The text was updated successfully, but these errors were encountered:
@ianb I assume this is caused when the time out limit is reached. Because we don't need to listen for audio input we should probably just remove the timeout for type input.
Prerequisites:
Mic permissions are enabled.
STR:
Expected result:
The "Doorhanger" displays the type input.
Actual result:
The "Doorhanger" displays the "Sorry, there was an issue" text after around 4 seconds and type input is not visible anymore.
Notes:
Reproduced on Mac 10.14.6 and Win10x64 with Firefox Nightly 71.0a1 (64-bit).
The written command can be continued and results will be shown after pressing "Enter" in both the "Doorhanger" and in new opened tabs, but the continuation of the command will not be visible when it's written.
Sometimes the "Sorry, there was an issue" text is displayed after around 8 seconds after the written command was started.
The text was updated successfully, but these errors were encountered: