Your Windows build number:
10.0.18362.86
What you're doing and what's happening:
What's wrong / what should be happening instead:
Input should be sent to the active console.
Where _specifically_ are you clicking to focus the window?
I'm seeing that clicking in the main part of the terminal window (with the text) works to send focus, but clicking anywhere in the tab row does _not_ focus the terminal control
@zadjii-msft Yes. I realized it only occurs when clicking the tab row. However, is this by design?
Btw, before I forget; I really love what you're doing with this project! The Windows Terminal is super fast!
That's good to know! Makes fixing it a lot easier. It's definitely not by design, I just need to know what UI element we need to eat the focus from :P
Thanks for the kind words! We're really happy to be able to make this for the community (and ourselves :P)
Found a few scenarios to lose focus (I suspect these to be basically the same problem):
This also happens with
Windows build number: 10.0.19018.0
Windows Terminal version (if applicable): 0.6.2951.0
When the Terminal regains focus by either clicking the title bar, any tab or the app icon in the task bar, then only the window is focused, not the active terminal, preventing you to type text into it.
Hey wadda ya know, this might just be related to #1205, which I just started on this morning. I'll make sure to include these scenarios in my investigations.
Moved to Windows terminal this week, loving it, but this is my biggest user-experience issue. I need to retrain my brain. Windows has trained me the safe way to focus any command window is by clicking the title-bar then the cursor will be in the correct place so i can type. I've typed so many characters into the ether this week
:tada:This issue was addressed in #3540, which has now been successfully released as Windows Terminal Preview v0.7.3291.0.:tada:
Handy links:
I'm still experiencing this issue. Exactly as described here and in #3609. Just switched to terminal hoping to make it my main, but this is really messing with me. My version:
Windows Terminal (Preview)
Version: 0.7.3451.0
I'm on 1903 (Build 18362.535)
Confirming that it's still happening for me as well. Looks like issue #3609 is still open and addressing this problem.