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
[Windows] Image is not centered in AspectFill mode #10645
Comments
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
This seems pretty basic to fix, not sure why this is in the backlog and not being fixed. Windows is still being treated like a platform that isn't supported. |
Verified this issue with Visual Studio 17.7.0 Preview 1.0. Can repro on windows platform with sample project. |
I can't get the grid workaround to work. Can you provide an example with MAUI xaml @japarson ? |
how is this still not fixed? |
…tform. (AspectFill not centered is a known issue: dotnet/maui#10645)
I am also running into this issue. I've been able to make some adjustments to the image's margin in the code behind to center then image, but it's a little laggy when resizing the window, not 100% correct, and not quite and ideal fix. |
Description
Image is not centered in AspectFill mode on Windows.
iOS and Android are OK.
Reproduced on ver. 6.0.541 (current) with Visual Studio 17.3.6
Attached:
MauiApp4 source code that demonstrates the bug:
MauiApp4.zip
Steps to Reproduce
Open attached MauiApp4 application that demonstrates the problem:
MauiApp4.zip
Link to public reproduction project repository
https://github.com/dotnet/maui/files/9766050/MauiApp4.zip
Version with bug
6.0.541 (current)
Last version that worked well
Unknown
Affected platforms
Windows
Affected platform versions
Windows SDK 10.0.19041
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: