-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[REGRESSION, 9.0.60 Android] Many labels are of wrong size #28928
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
Comments
Could this PR introduced some sort of regression for Android Labels? https://github.com/dotnet/maui/pull/28215/files#diff-3cca9c2b3a116c764c1a2d6f117cf6329ac7ca15aa10438a86c8d9f47f220c50. |
This is a UI bug we have had to rollback on, its causing some of our page content to expand way beyond their expected sizes when they have nested labels |
Same issue here |
1 similar comment
Same issue here |
Is there any expected release date for SR5.1 ? We cannot update to 9.0.60 due to the Android label regression mentioned in this ticket. We cannot revert to 9.0.50 because of the |
I had to roll back too, my app has many strings and Android UI is now a disaster under 9.0.60. |
Did you guys find any workaround or just rolled back to the previous versions? |
Just rolled back to 9.0.50 and waiting for the release of 9.0.70. Not sure if anything else can be done about this one. |
Rolled back |
One workaround that has helped with specifically labels that only have one line of text (multi-line text is still an issue) is adding LineBreakMode="NoWrap". EDIT: Looks like this workaround may rely on a few things. If you are wanting to use HorizontalOptions="End", use "HorizontalOptions="Fill" (should be default on a Label) and HorizontalTextAlignment="End" instead. |
Same problem.
Yes, that's it. @rmarinho @jsuarezruiz @PureWeen |
When I switch Label.IsVisible from False to True, due to the changes introduced in #28215, the incorrect LineCount is being used in the OnMeasure method to calculate maxWidth. This happens because, when the label is not visible, it uses the incorrect LineCount. After switching IsVisible to True, OnMeasure is not triggered again, and as a result, the displayed content is incorrect. Temporary Solution:
|
@janne-hmp I believe this issue has been addressed by this PR #29210 |
@janne-hmp You can test this issue with the PR #29210 fix in your app by following the steps in this @jfversluis video: https://youtu.be/B2FOBjZKm9k?si=Yuy5stjb5HnG1kPp |
Thanks for the note. There seems to be a YouTube video for everything these days. |
@jfversluis @jsuarezruiz do you know when SR7 will be released? |
we're targeting early next week |
@PureWeen @jfversluis @jsuarezruiz This has not been fixed in 9.0.70. Several labels are still of the wrong size on Android, so we are still stuck with 9.0.50. Can you please reopen the issue, or shall I make a new regression issue for 9.0.70? |
@PureWeen @jfversluis @jsuarezruiz This seems like a fundamental flaw since 9.0.60. I tried reworking some of my layouts so that they would work in Android, but ended up reverting to 9.0.40 (my previous version) because I could not get wrapped labels to stop consuming the remaining space. Why is what worked in 9.0.40/50 not working since 9.0.60. I can't upgrade until this is fixed. |
Tested 9.0.70 on our project. The issue is still not resolved. Reverting this PR fixes the bug. |
If possible please log a new bug with a repro using 9.0.70 |
Description
When upgrading from 9.0.50 to 9.0.60 several labels on Android, especially in titles, have started to malfunction by making the labels extremely narrow even though there is much space available. Windows and iOS seem to work properly.
Steps to Reproduce
Link to public reproduction project repository
https://github.com/hyvanmielenpelit/GnollHackMAUIEasyBuild
Version with bug
9.0.60 SR6
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
9.0.50 SR5
Affected platforms
Android
Affected platform versions
Android 15
Did you find any workaround?
No, cannot upgrade to 9.0.60 on Android.
Relevant log output
The text was updated successfully, but these errors were encountered: