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

Tab bar should better indicate that the window is active without needing the extra title bar #11709

Closed
markusjevringsesame opened this issue Nov 8, 2021 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@markusjevringsesame
Copy link

markusjevringsesame commented Nov 8, 2021

Description of the new feature/enhancement

In at least Windows 11, there's very little visual distinction between active and inactive windows. Since the tab bar is also the title bar by default, it would be nice if it did a better job of indicating whether the window is active or not. Right now I have resorted to enabling the title bar for the window just to see the accent color, but this makes it unnecessarily tall. It would be nice if the tab bar could, in some way, display the active highlight color when focused. Today all we have is a slight accented outline, and it would be nice to at least have the option of indicating more strongly that the window is active. Preferably in the tab bar.

Proposed technical implementation details (optional)

Change the color of the tab bar when active, potentially. Obey the accent color.

@markusjevringsesame markusjevringsesame added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 8, 2021
@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 Nov 8, 2021
@zadjii-msft
Copy link
Member

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

/dup #4862

@ghost
Copy link

ghost commented Nov 8, 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 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 Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants