-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
style: refine sticky header on the artist and album detail pages #444
Conversation
72fbcb2
to
aade5b6
Compare
add appbarbutton styles
aade5b6
to
a78ce66
Compare
Notice the header jitter while scrolling. ApplicationFrameHost_C3HNSwG9d8.mp4Also you can see the text flowing behind the header at the top edge. This is why I put the Header element on the same level as the ListView, and not as the ListView's Header. The ListView actually terminates before reaching the top edge . |
The new header also breaks keyboard navigation as it hides the focus highlight. ApplicationFrameHost_C7OUc0Cg9m.mp4 |
Changed to be consistent with the rest of the app headers. If anything now it's more pronounced, it got bumped from 28 to 32 font size.
Yeah sometimes it "bounces", I attempted to use
Yep, I think it's because of said "bouncing", or maybe scaling related, but I always got that 1 pixel line visibility issue.
I tried to minimize this as much as possible (obscures, at maximum, 2 items) but it's the nature of this type of header behavior. |
You misread. I said artist name, which I just noticed you changed the font size to body text in the minimal state.
Not really, even when we fix the top 1 pixel, you will still see the ListView behind the top 2 corners due to our corner radius > 1 pixel
This is not true. You can see in other parts of the app how ListView behaves when the mini-player is visible. |
Yep, my bad.
Right, it introduces a fixed padding. That would be ideal but it can't be "fixed" since it doesn't take into account the possibility of changes to text size. |
d1467e3
to
2ced3df
Compare
2ced3df
to
bf2e3ec
Compare
<!-- Uniform padding to ensure the text baseline aligns with TextBlocks (Caption) that have centered vertical alignment --> | ||
<Thickness x:Key="HyperlinkButtonUniformPadding">11,6.75,11,6.75</Thickness> | ||
|
||
<Thickness x:Key="SplitButtonPadding">12,6,12,7.11</Thickness> | ||
<Thickness x:Key="SplitButtonPadding">12,6,12,7.05</Thickness> |
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.
What's up with the fractional values? Are these values from WinUI?
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.
It is to keep the same height, and for the SplitButton also the content baseline, as the Button across all scales. However, it is not always perfect, as there can be discrepancies at either X25% or X75% scales.
No they are not from WinUI.
No description provided.