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

Glitch on tab close #10378

Closed
JekRock opened this issue Jun 9, 2021 · 3 comments
Closed

Glitch on tab close #10378

JekRock opened this issue Jun 9, 2021 · 3 comments
Labels
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

@JekRock
Copy link

JekRock commented Jun 9, 2021

Windows Terminal version (or Windows build number)

1.8.1521.0 and 1.9.1523.0

Other Software

No response

Steps to reproduce

  1. Open two tabs in the Windows Terminal (it doesn't matter what tabs)
  2. Switch to the first tab
  3. Close the second tab

Expected Behavior

When the second tab is closed, the first tab is rendered correctly and has the appropriate size.

Actual Behavior

When the second tab is closed, the first tab is rendered as if it has double size (it expands to the size of the second tab that was closed).
When the mouse is moved outside of the expanded first tab, the first tab is rendered as a single-size tab.

Before closing the second tab:
image

After the second tab is closed and the mouse pointer remains at the same location:
image

After the mouse pointer moves out of the first tab:
image

I could reproduce this behavior with a different number of tabs. If there are more than two tabs, the issue is reproducible for the last two tabs.

Example for 4 tabs
Before closing the 4th tab:
image

Switching to the 3rd tab and closing the 4th:
image

Moving the mouse cursor out of the 3rd tab that was expanded:
image

Note that when there are more than 2 tabs all the tabs get expanded.

The issue is reproducible for any Windows Terminal window size.

@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 Jun 9, 2021
@skyline75489
Copy link
Collaborator

I think this is the same issue described in #10101 (comment)

@zadjii-msft
Copy link
Member

Yep, this is definitely the same as that one. See also #9822

/dup microsoft/microsoft-ui-xaml#4971

@JekRock
Copy link
Author

JekRock commented Jun 9, 2021

Overlooked that, sorry. Closing the PR

@JekRock JekRock closed this as completed Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

3 participants