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

Created on 25 Apr 2020  ·  16Comments  ·  Source: microsoft/terminal

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

Area-Input Area-User Interface Issue-Bug Priority-3 Product-Terminal Resolution-Fix-Committed

Most helpful comment

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

Not even Ctrl + Shift + T works

All 16 comments

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

Not even Ctrl + Shift + T works

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

Hello @Sandra2001,
I am very focused on learning. It sometimes happens that I answer a question later.

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

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

@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.

@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.

_huh_

@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 ":+1:" button.

This might have gotten better with #5799/#5809 - if it didn't, then this will certainly be a similar class of issue.

EDIT: No, it didn't, but I bet this is because of the if (!dragging) check we do when the tab selection changes.

Almost certainly. Thanks for investigating!

@DHowett-MSFT I have added a GIF to better understand the problem.

Thanks.

@DHowett-MSFT You're welcome. :)

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

:tada:This issue was addressed in #5883, which has now been successfully released as Windows Terminal Preview v1.1.1671.0.:tada:

Handy links:

:tada:This issue was addressed in #5883, which has now been successfully released as Windows Terminal v1.0.1811.0.:tada:

Handy links:

Was this page helpful?
0 / 5 - 0 ratings