Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Size of newly started Quake mode window? #10622

Closed
vefatica opened this issue Jul 12, 2021 · 3 comments
Closed

Size of newly started Quake mode window? #10622

vefatica opened this issue Jul 12, 2021 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@vefatica
Copy link

vefatica commented Jul 12, 2021 •
edited
Loading

Windows Terminal version (or Windows build number)

Microsoft Windows 10 Pro for Workstations 10.0.19042.1083 (2009, 20H2) WindowsTerminal: 1.9.1445.0

Other Software

No response

Steps to reproduce

Press Win+` to open the Quake window.

Expected Behavior

I have two 1920x1080 monitors side by side. Given that the quake window is on one monitor, I expect NOT to see parts of it on the other monitor.

Actual Behavior

The Quake mode window is wider than the monitor. If it's on the left monitor, it's left edge is off the screen and it's right edge (windows highlight/shadow) is on the right monitor ... if it's on the right monitor, it's the reverse of that. Here's what Windows reports about its positon when it's on the left monitor (1920x1080).

LTRB: -8 0 1928 545
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 12, 2021
@vefatica
Copy link
Author

This seems to be a duplicate of #10201.

@zadjii-msft
Copy link
Member

Yep, sure looks like it. Thanks!

/dup #10201

@ghost
Copy link

ghost commented Jul 13, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 13, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 13, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @vefatica