terminal: Windows Terminal blocks user input after a tab is removed

Environment

Windows build number: 10.0.18363.815
Windows Terminal version (if applicable): 0.11.1121.0

Any other software?

Steps to reproduce

  • Start Windows Terminal
  • Open a new Windows PowerShell tab
  • Now drag the tab to a location without releasing the tab
  • Now close the tab with this key combination Ctrl + Shift + W
  • Now try to make an input in the command line on the first tab, or try a key combination.

Expected behavior

  • Windows PowerShell should allow input.
  • Windows Terminal should allow keyboard input after trying to create a new tab with the key combination Ctrl + Shift + T.

Actual behavior

  • Windows PowerShell does not allow input.
  • Windows Terminal does not allow keyboard input after you try to create a new tab with the key combination Ctrl + Shift + T.

ezgif-7-9b0200dbcf4a

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 6
  • Comments: 16 (6 by maintainers)

Commits related to this issue

Most upvoted comments

All right, I’d say that’s a bug. 😲🤯

Not even Ctrl + Shift + T works

Now, do I know who found this problem. DHowett Thanks for the help

@IamAIQ please stop posting the same comment on all of our issues. If you would like to subscribe, please click the “Subscribe” button. If you would like to add your support, please click the “👍” button.

@DHowett The application reacts first when a new tab is created by clicking the “+” button. The application also does not react to key combinations as described above.

@DHowett

  1. No, the application does not react when clicked in the terminal.
  2. No, this message “this program is not responding” is not displayed.

If you click inside the terminal, does it start responding again?

Do you see the Windows “this program is not responding” message?

@Qantex Why are you always ### busy??