-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[regression/8.0.0-preview.1.7762] CollectionView with bound text of varying lengths does not properly measure all items #16234
Comments
I believe I'm getting the same issue but also on version 7.0.92. It started happening after I updated a bunch of packages which probably included MAUI stuff. the last working version for me is 7.0.86. i reverted back to it by adding this to the .csproj: |
@manstheram I did not see this issue on 7.0.92 with my reproduction project. Can you link yours, possibly? Thanks! |
@samhouts |
Hello lovely human, thank you for your comment on this issue. Because this issue has been closed for a period of time, please strongly consider opening a new issue linking to this issue instead to ensure better visibility of your comment. Thank you! |
Description
I have a CollectionView with a Label in the ItemTemplate. The text of the Label is bound to a value in the ItemSource that can either be 1 line or multiple lines. As of 8.0, it appears that it only measures the first item in this instance and not all items, so if the first item is short, the rest of the items will be cut off.
Works as expected in 7.0.92.
Steps to Reproduce
Expected: CollectionView has rows of varying height and the entire content is visible.
Actual: CollectionView has rows of all the same height and some of the content is truncated.
Link to public reproduction project repository
https://github.com/samhouts/dotnetmauirepros/tree/cvmeasureallitems
Version with bug
8.0.0-preview.1.7762
Last version that worked well
7.0.92
Affected platforms
Android, Windows, I was not able test on other platforms
Affected platform versions
?
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: