-
Notifications
You must be signed in to change notification settings - Fork 678
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
Two identical syncronized <ScrollViewer> components don't align #9817
Comments
Does it repro with display scaling set to 100%? |
@kmgallahan - no, it doesn't. At Display scaling 100% they align perfectly ... |
That means layout rounding is used when the UI is scaled, and the positioning logic is different when handling input vs values set via code. |
@kmgallahan - ok, thanks ... Does that mean it is "works as designed", or that a fix will be created? |
Most 'off by a pixel' stuff is related to scaling, so I just wanted to check if that was the case here. Otherwise, I'm not an MS employee so no idea how they are allocating funding to resolve misc. aesthetic issues. |
@kmgallahan - ok, thanks Kevin :) |
Describe the bug
I have two ScrollViever components side by side, each containing a StackPanel with the same number of elements all of the same size. The two ScrollView components are synchronized through the ViewChanged event.
When one ScrollViewer is scrolled all the way to the bottom, the two ScrollViewer components are misaligned by one or two pixels. Scrolling the last pixel in the ScrollViewer I am scrolling does not trigger the ViewChanged event.
Steps to reproduce the bug
See the following XAML / C# code:
Expected behavior
The two should move totally synchronized since the animation is disabled. When you try to scroll them all the wqy to the bottom you will see that one is misaligned by one or two pixels.
Screenshots
NuGet package version
WinUI 3 - Windows App SDK 1.6 Experimental 2: 1.6.240701003-experimental2
Windows version
No response
Additional context
My WIndows Version is 23H2
The text was updated successfully, but these errors were encountered: