Windows-up does not maximize window (focus mode?)

[chipbite]

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.4061]

Other Software

NA

Steps to reproduce

1. start windows terminal, e g with win-r, wt (press enter) Situation: window starts in a free/"undocked" mode - i e not "docked"/aligned to any side of the screen.
2. Press win-left (or right) to position window aligned with a side. Situation: window is now (a) "docked"/aligned to the side of the screen and (b) expanded to use all of the screen height
3. press windows-up (arrow) once, to make window half height Situation: window is now (a) aligned to the side and top of the screen and (b) vertically it is now half the screen height.
4. press windows-up (arrow) again, a second time - to maximize the window

My settings: always focus mode/title bar off, tabs off...

Please see attached screencapture.

Expected Behavior

window maximizes

Actual Behavior

window remains in place, no change to position, alignment or size.

Workarounds

• Alt-space, x chord works fine (legacy way of maximizing a window)
• Full-screen mode works (E g f11)

---

Off topic: Thanks for frameless!

I really love how the windows terminal enables me to run frameless windows via focus mode. Thanks alot for that!!

Example setup pic:

https://github.com/microsoft/vscode/issues/174903#issuecomment-2920655729

[jamespack]

This works on windows 11. I noticed you're not passing any args. Did you try passing --focus to it?

We have nearly the same build number.

[chipbite]

Hi James! Thanks alot for reading!

This works on windows 11.

No, this is win 11. I suspect you misunderstand: Windows build number 10.0.26100.4061 is windows 11, 24H2. (win 11 build nrs are seemingly above 20000, I am guessing, so 10.0.20000+ is no longer win10, it seems. There are many resources on build numbers, example)).

I noticed you're not passing any args. Did you try passing --focus to it?

I am not sure I understand this comment. I have windows terminal configured to focus mode being always on (paragraph 3, here). And that works, it starts in focus mode. Passing the same thing as a parameter seems redundant, not sure if that would give any better view of the problem?

We have nearly the same build number.

Right, see my comment above. I suspect alot of people assume that the major version 10.0 = win 10, which is certainly not unreasonable. In fact several different windows OS products share major version 10.0.

Anyway, the behavior is totally consistent om my machine. I suspect to repro, the key elements are to have focus mode setup, etc. I suspect reproducing should be straightforward, will try on a few other machines later in the next work week.

[jamespack]

Thanks for teaching me how to default to Focus mode! Thats pretty dope. Unfortunately, it still works for me :(

Im not confused about build numbers. I was simply stating our build numbers are close and I am on Windows 11 and it works. Sorry for the confusion.

[jamespack]

Working Build

OS: 10.26100.4202 Terminal: 1.22.11141.0 Not sure if these will be helpful for the team but just in case.

https://github.com/user-attachments/assets/a157436c-aa83-49ab-bba9-f61abeb89b67

[mawid6]

Thanks for checking it out! Odd that you cant reproduce, I wonder what the secret ingredient is.

I found a workaround, which is to use the good old alt-space, x chord. It seems to work fine, but win-up does not, for me...

[DHowett]

Hmm. While we try to figure out what the underlying issue is, I have a few questions:

• Are you using any shell extensions that change windowing behavior? Replace the taskbar/?
• Does F11 or Alt+Enter work to kick the window into fullscreen (though I recognize that this is more maximized than you'd like)

FWIW: We can't reproduce this here, even on 10.0.26100 🙂

Though, while trying to reproduce it I did manage to make a window that doesn't respond to Win+Up or Win+Down at all, but still responds to Win+Left/Right. Huh.

[chipbite]

Hi!

* Are you using any shell extensions that change windowing behavior? Replace the taskbar/?

No, I dont think so. I use powertoys but have disabled all the windowing related tools.

* Does F11 or Alt+Enter work to kick the window into fullscreen (though I recognize that this is more maximized than you'd like)

Yes, they work. As I said above, so does e g alt-space + x chord.

FWIW: We can't reproduce this here, even on 10.0.26100 🙂

I will try and see if I can repro on some colleagues computers tomorrow.

Though, while trying to reproduce it I did manage to make a window that doesn't respond to Win+Up or Win+Down at all, but still responds to Win+Left/Right. Huh.

Odd. For me it is just that win-up consistently moves the half-screen-width window to the top-half, making it quarter screen sized, as the screen-capture above shows.

[jamespack]

Odd. For me it is just that win-up consistently moves the half-screen-width window to the top-half, making it quarter screen sized, as the screen-capture above shows.

Oh.. I think that's the default behavior. At least that's what I see from half size If you hit the key chord again does it maximize?

[chipbite]

Odd. For me it is just that win-up consistently moves the half-screen-width window to the top-half, making it quarter screen sized, as the screen-capture above shows.

Oh.. I think that's the default behavior. At least that's what I see from half size If you hit the key chord again does it maximize?

Yes - I meant subsequent win-up presses, not the initial one. The initial win-up press moves the window to the top half, which is correct and as expected, as you note.

This can be seen in the screencapture above, i e: All subsequent win-up presses do nothing.

~~I will clarify this in the text of the post!~~

I have clarified the repro in the post, to be clear on this!

Thanks!

[jamespack]

Thx for clarifying.

[Philipp01105]

Tested it on my Machine (10.0.26100.4349) and is also not reproduceable

[chipbite]

OT: Alright, alright, alright! Its FRIIDAYYY! 😁😁

So, after all of this whiiining going on ooh, I cant repro, oooooh, I cant repro.... 😉😂

Sorry, jokes aside - and my apologies for not getting back sooner!

@Philipp01105: Thanks for reading and testing it out, btw!

I finally took the time to look into this to clarify the repro. I was lucky, I think I found the combination of settings that causes this and in so doing, I also found a perfect workaround for me. I will update the report above, but it turns out that:

Configuring windows terminal to use BOTH of these two settings triggers it:

1. Startup, Launch parameters: Focus (I have Focus, let windows decide on location) and
2. Appearance tab, Hide the title bar

causes the problem to appear (ie cannot maximize with win-up).

I arrived at these settings through just trying them out. I did not realize that if I have Focus as launch, it seems I don't need Hide the title bar, since Focus hides title bar anyway. And with just Focus set, win-up works fine.

So, there might be a bug wrt win-up when both of these are set. That said, the workaround is easy and solves my problem.

Thanks! Have a nice weekend!

[Philipp01105]

@chipbite So I just tested it with both of these settings on (hide title bar and also --focus parameter also tested it with the setting) and i still cant reproduce it, just so you know. Maybe its a local issue with another config or process on your machine? Cant remember if anyone in the issue coudl repro it.

[chipbite]

Gah. I have reproduced this now on 2 machines (company and client, both win 11), so that is odd. I will check again, maybe there is a third setting I must have set.

[Philipp01105]

Tested it on my Machine (10.0.26100.4349) and is also not reproduceable

also no problem on 26100.4652 (home machine)

[chipbite]

Yeah, now it is gone for me, and works well. Cannot repro in new machine.