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.

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

Remove margin over tabs on second (scaled) display #13205

Closed
r-bird opened this issue May 30, 2022 · 1 comment
Closed

Remove margin over tabs on second (scaled) display #13205

r-bird opened this issue May 30, 2022 · 1 comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@r-bird
Copy link

r-bird commented May 30, 2022

Windows Terminal version

1.12.10982.0

Windows build number

10.0.19042.1706

Other Software

No response

Steps to reproduce

  1. connect a second display
  2. extend your desktop to it (WIN+P -> Extend)
  3. open a terminal with two tabs
  4. move the terminal window to the second display and maximize it
  5. move your cursor to the very top of the screen above the inactive tab and click it

Expected Behavior

The inactive tab should become active - just like it does on the primary display.

Actual Behavior

The window border is clicked, not the tab.
You have to move your cursor down a few pixels to click the tab.

@r-bird r-bird added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 30, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 30, 2022
@zadjii-msft
Copy link
Member

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #11309 for more discussion.

/dup #11309

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants