You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I upgrade to v1.2.0 from v1.1.1 but I found weird behavior that I can confirm not from windows terminal, already try windows terminal 1.7, 1.8, 1.9-preview, but no avail. I use full screen, always on top, hide on lost focus
The problem is when I focus other window and the quake hide, when I toggle open again, the cursor become on top rather than showing previous scroll, expected like this:
But instead got this
The cursor always on top and hide everything before it, I need to scroll to see previous command and result. This also happen when I start to type, the window instantly focus to current input, and make the input on top, again, hiding everything before it.
v1.1.1 doesn't have this issue
Quake config, but I recently learned that using vanilla config also have this issue:
@fmiqbal Thank you for reporting this issue! I think this might be due to the recently added different toggle mode, could you try to add the following and see if it changes anything?
The default toggle mode has been changed to "Move", on version 1.3.0, to prevent this issue, seeing that there are perhaps more cases of this then vertical monitor setups, which was the reason for the "Resize" mode.
Recently I upgrade to v1.2.0 from v1.1.1 but I found weird behavior that I can confirm not from windows terminal, already try windows terminal 1.7, 1.8, 1.9-preview, but no avail. I use full screen, always on top, hide on lost focus
The problem is when I focus other window and the quake hide, when I toggle open again, the cursor become on top rather than showing previous scroll, expected like this:
But instead got this
v1.1.1 doesn't have this issue
Quake config, but I recently learned that using vanilla config also have this issue:
Windows 10 Version Dev (OS Build 21390.2025)
The text was updated successfully, but these errors were encountered: