Currently-active tab isn't always visible in the tab bar #12061

Closed
opened 2026-01-31 03:05:17 +00:00 by claunia · 4 comments
Owner

Originally created by @austin-beer on GitHub (Jan 13, 2021).

Environment

Windows build number: 10.0.18363.1198
Windows Terminal version (if applicable): 1.5.3242.0

Steps to reproduce

  1. Set tabSwitcherMode to "disabled" in settings.json.
  2. Open enough tabs that you have to scroll the tab bar to see them all.
  3. Use the keyboard to cycle through all of the tabs.

Expected behavior

The currently active tab is always visible in the tab bar. This requires that the tab bar sometimes scroll itself so that the currently active tab remains visible.

Actual behavior

The currently active tab is not always visible.

Originally created by @austin-beer on GitHub (Jan 13, 2021). # Environment ```none Windows build number: 10.0.18363.1198 Windows Terminal version (if applicable): 1.5.3242.0 ``` # Steps to reproduce 1. Set tabSwitcherMode to "disabled" in settings.json. 2. Open enough tabs that you have to scroll the tab bar to see them all. 3. Use the keyboard to cycle through all of the tabs. # Expected behavior The currently active tab is always visible in the tab bar. This requires that the tab bar sometimes scroll itself so that the currently active tab remains visible. # Actual behavior The currently active tab is **not** always visible.
Author
Owner

@zadjii-msft commented on GitHub (Jan 14, 2021):

This seems reasonable. That being said, I'm not sure we can do this with the TabView currently. It almost seems like something the TabView should be doing for us. I'll file something upstream, since it doesn't look like there are any existing issues.

Upstream issue: https://github.com/microsoft/microsoft-ui-xaml/issues/3945

@zadjii-msft commented on GitHub (Jan 14, 2021): This seems reasonable. That being said, I'm not sure we can do this with the `TabView` currently. It almost seems like something the `TabView` should be doing for us. I'll file something upstream, since it doesn't look like there are any existing issues. Upstream issue: https://github.com/microsoft/microsoft-ui-xaml/issues/3945
Author
Owner

@Don-Vito commented on GitHub (Jan 16, 2021):

@austin-beer , @zadjii-msft - this looks very similar to #3638

@Don-Vito commented on GitHub (Jan 16, 2021): @austin-beer , @zadjii-msft - this looks very similar to #3638
Author
Owner

@zadjii-msft commented on GitHub (Jan 19, 2021):

It sure is! Thanks!

/dup #3638

@zadjii-msft commented on GitHub (Jan 19, 2021): It sure is! Thanks! /dup #3638
Author
Owner

@ghost commented on GitHub (Jan 19, 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 commented on GitHub (Jan 19, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12061