Windows Terminal blocks user input after a tab is removed #7680

Closed
opened 2026-01-31 01:10:14 +00:00 by claunia · 16 comments
Owner

Originally created by @avdain on GitHub (Apr 25, 2020).

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

Originally created by @avdain on GitHub (Apr 25, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none 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. <!-- A description of how to trigger this bug. --> # 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**. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # 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](https://user-images.githubusercontent.com/47790579/81594415-23fd5e80-93c1-11ea-8346-d448fed6f31e.gif) <!-- What's actually happening? -->
Author
Owner

@Sandra2001 commented on GitHub (Apr 25, 2020):

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

Not even Ctrl + Shift + T works

@Sandra2001 commented on GitHub (Apr 25, 2020): All right, I'd say that's a bug. **😲🤯** ### Not even Ctrl + Shift + T works
Author
Owner

@Sandra2001 commented on GitHub (Apr 25, 2020):

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

@Sandra2001 commented on GitHub (Apr 25, 2020): @Qantex Why are you always ### busy??
Author
Owner

@avdain commented on GitHub (Apr 25, 2020):

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

@avdain commented on GitHub (Apr 25, 2020): Hello **@Sandra200**1, I am **very focused on learning**. It sometimes happens that I answer a question later.
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 25, 2020):

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

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

@DHowett-MSFT commented on GitHub (Apr 25, 2020): If you click inside the terminal, does it start responding again? Do you see the Windows “this program is not responding” message?
Author
Owner

@avdain commented on GitHub (Apr 26, 2020):

@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.
@avdain commented on GitHub (Apr 26, 2020): @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.
Author
Owner

@avdain commented on GitHub (Apr 26, 2020):

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

@avdain commented on GitHub (Apr 26, 2020): @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.
Author
Owner

@zadjii-msft commented on GitHub (Apr 27, 2020):

huh

@zadjii-msft commented on GitHub (Apr 27, 2020): _huh_
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 28, 2020):

@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-MSFT commented on GitHub (Apr 28, 2020): @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.
Author
Owner

@zadjii-msft commented on GitHub (May 8, 2020):

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.

@zadjii-msft commented on GitHub (May 8, 2020): 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.
Author
Owner

@DHowett-MSFT commented on GitHub (May 8, 2020):

Almost certainly. Thanks for investigating!

@DHowett-MSFT commented on GitHub (May 8, 2020): Almost certainly. Thanks for investigating!
Author
Owner

@avdain commented on GitHub (May 11, 2020):

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

@avdain commented on GitHub (May 11, 2020): @DHowett-MSFT I have added a **GIF** to better understand the problem.
Author
Owner

@DHowett-MSFT commented on GitHub (May 11, 2020):

Thanks.

@DHowett-MSFT commented on GitHub (May 11, 2020): Thanks.
Author
Owner

@avdain commented on GitHub (May 11, 2020):

@DHowett-MSFT You're welcome. :)

@avdain commented on GitHub (May 11, 2020): @DHowett-MSFT You're welcome. :)
Author
Owner

@EugeneLockett commented on GitHub (May 12, 2020):

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

@EugeneLockett commented on GitHub (May 12, 2020): Now, do I know who found this problem. DHowett Thanks for the help
Author
Owner

@ghost commented on GitHub (Jun 18, 2020):

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

Handy links:

@ghost commented on GitHub (Jun 18, 2020): :tada:This issue was addressed in #5883, which has now been successfully released as `Windows Terminal Preview v1.1.1671.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.1.1671.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Jun 30, 2020):

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

Handy links:

@ghost commented on GitHub (Jun 30, 2020): :tada:This issue was addressed in #5883, which has now been successfully released as `Windows Terminal v1.0.1811.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.0.1811.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7680