-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Reorder the color chips grid in the color schemes page #14223
Conversation
So uh.. I'm not sure this is the best design choice. The most important info is the color scheme name, which should be the left-most item. Is there something else we can do to get around this bug? |
I would argue that the most important part of a color scheme is the colors. The name is secondary, and users will use whichever one has the colors they want. Konsole chose to put the preview to the left of the name as well, in their appearance list. |
Perhaps we could experiment with putting the colors under the name? Windows loved a chonky list item. |
The problem is caused by a XAML bug that only affects Windows 10. I remember seeing Pankaj try and bind to the Like Dustin said, Konsole has the preview to the left so this isn't necessarily bad. My main issue with it is the color chips because they're too big. I hate to say it, but maybe we should remove the color chips? |
Hard no from me! They bring so much value to this page -- you can make a color scheme selection based on the look alone, without having to open one up and remember what it looked like. |
(Personally, I think I love "full width chip" #-1 with the colors on the left) |
I kinda agree with Leonard, but I worry about schemes with bad fg/bg contrast (but then, that's kinda on them) |
As a follow up, I'll be adding that treament to the color scheme dropdown in the profile->appearance page |
I kinda like the 8x8 color chips with This slightly violates the suggestion Leonard made where the colored box would take up 75% of the height of the cell. We were prototyping with a 48px cell height and a total height of.. 32? |
I prefer the larger spacing and larger color chips tbh! Makes it a lot easier on the eyes (I feel like I need to squint for the smaller chips/spacing one). I can make the left margin bigger to have all the margins be the same. Yeah this new one takes more than 75% of the height but I like it for the improved visibility! Happy to change it if the consensus is we prefer the other one though |
Hmmmm. So, my attempt was with 8. What if we try 10 or 12? Down from 15, but still not as big as 15. I'm worried that keeping the chips on the bigger side doesn't help @carlos-zamora / @cinnamon-msft's concern about the text being too far away from the left side. What does it look like with Size 12 Padding 1? |
Padding="10,0,10,0" | ||
HorizontalAlignment="Center" | ||
VerticalAlignment="Center" | ||
AutomationProperties.AccessibilityView="Raw" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that this is the only copy of the color scheme name in the UI, we need to do one of two things.
- We need to make the entire tree
Raw
and setAutomationProperties.Name="{x:Bind Name, Mode=OneWay}"
on the root element in theDataTemplate
(actually, this might be the right way to go)
or
- this can't be
Raw
I saw tactic 1 in use in another application, but I can't remember which. It could be a really good way to ensure that a11y tools see the entire UI element as a single thing named "Campbell" or "One Half Dark". Maybe there's even a way to set the AutomationProperties.ItemType
to color scheme
or something. @carlos-zamora cc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current implementation works as expected, actually. Looks like the list view is somehow applying the names to the list view item itself.
That said, the "default" tag isn't being read out. I don't think that's new though and I'm not sure how to fix it. You may need to bind the list view item like Dustin said in (1) above, but have the "name"
be set to "<name> <defaultTag (if present)>"
. Alas, that can probably be a follow-up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Relevant: #13891
I think it looks fine but I have to admit I don't have the eye for this kind of stuff. My concern about the text being too far away from the left side is resolved though. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not blocking, but I have a few questions/comments.
Also, here's another thing I don't know about. If the user enters high contrast mode, we can't guarantee the text here is in high contrast. Is that ok? I'm concerned about the use case for a newly installed terminal. On one hand, it's nice to be see which ones have a high enough contrast and which ones don't. On the other, maybe the right thing to do is to show the names in a high-contrast format? idk.
HorizontalAlignment="Center" | ||
VerticalAlignment="Center" | ||
AutomationProperties.AccessibilityView="Raw" | ||
FontFamily="Cascadia Code" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DHowett did we ever figure out what happens if we can't find Cascadia Code? Should we care?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, it falls back to Segoe UI or something. It's weird but not world-ending.
Padding="10,0,10,0" | ||
HorizontalAlignment="Center" | ||
VerticalAlignment="Center" | ||
AutomationProperties.AccessibilityView="Raw" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @zadjii-msft! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
XAML has an issue in windows 10 where `Width="*"` does not work properly inside the `DataTemplate` for a `ListView`. Because of this, the color scheme list view items looked very strange in windows 10 (see #14187). Thanks to that, we thought up a few new designs for the color schemes page and selected a new one that blends the color chips with a region that shows the foreground and background color with the text preview. Closes #14187 (cherry picked from commit 23a02c5) Service-Card-Id: 86518549 Service-Version: 1.16
🎉 Handy links: |
XAML has an issue in windows 10 where
Width="*"
does not work properlyinside the
DataTemplate
for aListView
. Because of this, the colorscheme list view items looked very strange in windows 10 (see #14187).
Thanks to that, we thought up a few new designs for the color schemes
page and selected a new one that blends the color chips with a region
that shows the foreground and background color with the text preview.
Closes #14187