Skip to content

[UX] Settings UI refinements #19001

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

Merged
merged 9 commits into from
Jul 23, 2025
Merged

Conversation

niels9001
Copy link
Contributor

@niels9001 niels9001 commented Jun 4, 2025

This PR is a (first) design pass on the Terminal settings UX to bring consistency and alignment with the rest of the OS and other settings surfaces.

High-level changes include:

  • Using WinUI brushes vs. UWP/OS brushes. See brushes overview in the WinUI 3 Gallery:.
  • Updating pixel values for margins, fontsizes, paddings etc. using units of 4. See the design guidelines for more info.
  • Adding rounded corners on various elements to be consistent with the Windows 11 look and feel (using the ControlCornerRadius or OverlayCornerRadius WinUI resources as much as possible).
  • Decreasing the page header titles / breadcrumb so it feels a bit less cramped.
  • Fixing a bug where the title of the page was not aligned with the content when resizing the window (note to self: should fix this in PowerToys too):
  • Ensuring the subheader texts for settings categories are inline with the rest of the OS (== decreasing the fontsize).

This comment has been minimized.

Copy link
Member

@carlos-zamora carlos-zamora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love all the changes you've made. Thank you so much!

There's just a few changes that I'm uncertain of. Added a comment and my thoughts. Let me know what you think. I'm excited to see this land soon!

Comment on lines -203 to +215
Margin="10,0,0,0"
Padding="2,0,2,0"
Margin="12,0,0,0"
Padding="8,4"
HorizontalAlignment="Left"
VerticalAlignment="Center"
Background="{ThemeResource SystemAltMediumLowColor}"
BorderBrush="{ThemeResource SystemControlForegroundBaseMediumBrush}"
Background="{ThemeResource SubtleFillColorSecondaryBrush}"
BorderBrush="{ThemeResource ControlStrongStrokeColorDefaultBrush}"
BorderThickness="1"
CornerRadius="1"
CornerRadius="{StaticResource ControlCornerRadius}"
Visibility="{x:Bind IsDefaultScheme, Mode=OneWay}">
<TextBlock x:Uid="ColorScheme_DefaultTag"
Grid.Column="1"
AutomationProperties.AccessibilityView="Raw"
Foreground="{ThemeResource SystemControlForegroundBaseMediumBrush}" />
Foreground="{ThemeResource TextFillColorSecondaryBrush}" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝
before:
image

after:
image

Copy link
Contributor Author

@niels9001 niels9001 Jun 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was the existing token style by design? In WinUI we use 4px as a minimum margin around text so it's legible. The brushes that were previously used are not part of WinUI but OS.

Comment on lines -59 to +62
<Setter Property="CornerRadius" Value="1" />
<Setter Property="Background" Value="{ThemeResource SystemAltMediumLowColor}" />
<Setter Property="BorderBrush" Value="{ThemeResource SystemControlForegroundBaseMediumBrush}" />
<Setter Property="CornerRadius" Value="{StaticResource ControlCornerRadius}" />
<Setter Property="Background" Value="{ThemeResource SubtleFillColorSecondaryBrush}" />
<Setter Property="BorderBrush" Value="{ThemeResource DividerStrokeColorDefaultBrush}" />
<Setter Property="Padding" Value="4,4,4,4" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm... I'm concerned these look a bit too much like buttons now:

before:
image

after:
image

Copy link
Member

@lhecker lhecker Jun 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does it need to be a different color anyway? Couldn't it just be a regular label / text?
If I had to pick between the two images though, I'd prefer the button style.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are actually working with the design team to figure this out; we have shortcut visualizations across PowerToys, Terminal and Windows itself - and things are a bit all over the place.

image

image

image

image

Once we have better specs for this, we can implement it here too? Shall I revert for now?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once we have better specs for this, we can implement it here too? Shall I revert for now?

I support this, revert for now and return to it once the design team has finalized what it should look like

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so did we revert it? I notice it's still in the "after" screenshots...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI @PankajBhojwani is actively working on this page over in #18917. We should make sure some of this styling is carried over in the new subpage.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jun 4, 2025
@DHowett
Copy link
Member

DHowett commented Jun 4, 2025

Quick gut check: Terminal runs on Windows 10 still. This doesn't change that, right?

Co-authored-by: Carlos Zamora <carlos.zamora@microsoft.com>
@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jun 5, 2025
@niels9001
Copy link
Contributor Author

niels9001 commented Jun 17, 2025

Quick gut check: Terminal runs on Windows 10 still. This doesn't change that, right?

Nope. all resources that are used are part of WinUI (2/3).

Copy link
Member

@carlos-zamora carlos-zamora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested the branch locally and went through some of the pages (i.e. Extensions, Profile > Appearance) and controls (i.e. nullable color picker settings) comparing them to what's in Canary. Looks good to me. Thank you so much for doing this 😊

Comment on lines 111 to 121
<!-- Used to stack a group of settings -->
<Style x:Key="SettingsStackStyle"
TargetType="StackPanel">
<Setter Property="Margin" Value="{StaticResource SettingStackMargin}" />
<Setter Property="MaxWidth" Value="{StaticResource StandardControlMaxWidth}" />
</Style>

<!-- Used to stack a group of settings inside a pivot -->
<Style x:Key="PivotStackStyle"
TargetType="StackPanel">
<Setter Property="Margin" Value="{StaticResource SettingStackMargin}" />
<Setter Property="MaxWidth" Value="{StaticResource StandardControlMaxWidth}" />
</Style>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh, looks like we can merge the two and just keep SettingsStackStyle around. PivotStackStyle was probably introduced back when we had a Pivot control ages ago.

If you're interested, feel free to do this as a part of this PR. Not a requirement though. More just something I took note of 😊

@carlos-zamora
Copy link
Member

Demo

These were originally in the PR body. Moved the images out into their own thread.

  • Fixing a bug where the title of the page was not aligned with the content when resizing the window (note to self: should fix this in PowerToys too):
    image

  • Ensuring the subheader texts for settings categories are inline with the rest of the OS (== decreasing the fontsize).
    image

A few before vs after screenshots:

image

image
image

@carlos-zamora carlos-zamora merged commit 48b796f into microsoft:main Jul 23, 2025
15 checks passed
DHowett pushed a commit that referenced this pull request Jul 23, 2025
Reverts most of the styling changes done in #19001 to the key chords
displayed in the SUI's Actions page. The `CornerRadius` was kept at the
updated value of `ControlCornerRadius` for consistency.

The only other changes in #19001 that were kept for this page include:
- `EditButtonIconSize`: 15 --> 14
- `AccentEditButtonStyle` > `Padding`: 3 --> 4
- Command name's `FontWeight` reduced to `Normal`
- `AddNewButton` > `Margin` added (set to `0,12,0,0` to provide spacing
between breadcrumb header and button)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants