Polish Settings UI: Very annoying functionality #12062

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

Originally created by @carlos-zamora on GitHub (Jan 12, 2021).

  • Go to any profile -> Go to Appearance or Advanced tab -> Hit 'Apply': SUI automatically switches to the General tab (can be annoying if the user just wants to check out what a setting does)
  • Appearance -> Open 'Color scheme' dropdown -> Cannot dismiss the dropdown by clicking somewhere else
  • tooltips on radio buttons currently describe entire set of options. Need descriptions on each individual setting options.
    • Case in point: What does "uniform to fill" mean? On Profiles/Appearance. It's impossible to know what these enum values really mean.
    • we got rid of these
Originally created by @carlos-zamora on GitHub (Jan 12, 2021). - [x] Go to any profile -> Go to Appearance or Advanced tab -> Hit 'Apply': SUI automatically switches to the General tab (can be annoying if the user just wants to check out what a setting does) - [x] Appearance -> Open 'Color scheme' dropdown -> Cannot dismiss the dropdown by clicking somewhere else - Moved to Light-dismiss doesn't work on ComboBox in XAML Islands https://github.com/microsoft/microsoft-ui-xaml/issues/3961 - [ ] tooltips on radio buttons currently describe entire set of options. Need descriptions on each individual setting options. - [ ] Case in point: What does "uniform to fill" mean? On Profiles/Appearance. It's impossible to know what these enum values really mean. - [x] we got rid of these
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalPriority-2Area-SettingsUI labels 2026-01-31 03:05:19 +00:00
Author
Owner

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

RE: the Profile pivot resetting

In a5a46af73, I'm doing something similar to how we want to fix this. We need to stash internal navigation state in the {page}NavigationState, and keep a singleton instance of each page's state in the MainPage. That way, we can have the Profiles page update the selected pivot within the NavigationState, and the next instance of Profiles will be able to look up that state.

@zadjii-msft commented on GitHub (Jan 13, 2021): RE: the Profile pivot resetting In a5a46af73, I'm doing something similar to how we want to fix this. We need to stash internal navigation state in the `{page}NavigationState`, and keep a singleton instance of each page's state in the `MainPage`. That way, we can have the `Profiles` page update the selected pivot within the NavigationState, and the _next_ instance of `Profiles` will be able to look up that state.
Author
Owner

@carlos-zamora commented on GitHub (Feb 12, 2021):

  • tooltips on radio buttons currently describe entire set of options. Need descriptions on each individual setting options.
    - [ ] Case in point: What does "uniform to fill" mean? On Profiles/Appearance. It's impossible to know what these enum values really mean.

So, this is a tough one. It looks like we can either do a single tooltip on the entire RadioButtons (note the plural) control, or on each individual RadioButton. Not both.

In general, we should make the choices and header as descriptive as possible to get around this issue. But that's not always possible, unfortunately.

I think we should go with the individual RadioButton descriptions and that way we can attach tooltips and automation properties to them. That's probably the cleanest way around this issue.

@carlos-zamora commented on GitHub (Feb 12, 2021): > - [ ] tooltips on radio buttons currently describe entire set of options. Need descriptions on each individual setting options. - [ ] Case in point: What does "uniform to fill" mean? On Profiles/Appearance. It's impossible to know what these enum values really mean. So, this is a tough one. It looks like we can either do a single tooltip on the entire `RadioButtons` (note the plural) control, or on each individual `RadioButton`. Not both. In general, we should make the choices and header as descriptive as possible to get around this issue. But that's not always possible, unfortunately. I think we should go with the individual `RadioButton` descriptions and that way we can attach tooltips and automation properties to them. That's probably the cleanest way around this issue.
Author
Owner

@zadjii-msft commented on GitHub (Apr 11, 2022):

RE: tooltips on radio buttons: The RadioButtons were removed in 1.13, so now we need to add the tooltips to the entries in the dropdown.

@zadjii-msft commented on GitHub (Apr 11, 2022): RE: tooltips on radio buttons: The RadioButtons were removed in 1.13, so now we need to add the tooltips to the entries in the dropdown.
Author
Owner

@zadjii-msft commented on GitHub (Aug 12, 2022):

Cannot dismiss the dropdown by clicking somewhere else

We got rid of almost all of these with Controlsv2. Except the default profile one...? (#13731)

@zadjii-msft commented on GitHub (Aug 12, 2022): > Cannot dismiss the dropdown by clicking somewhere else We got rid of almost all of these with Controlsv2. Except the default profile one...? (#13731)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12062