Trigger InvalidateMeasure event on CollectionView when content size changes (Windows and Android)

[albyrock87]

Description

When CollectionView is configured as *Options != Fill the DesiredSize depends on content size.
When content size changes InvalidateMeasure should be triggered to notify parent views/layout about changes in the desired size.

#24647 introduces such behavior on iOS to fix #21141 on iOS but the behavior should be consistent on all platforms.

Steps to Reproduce

Run device test CollectionViewCanSizeToContent by removing the #if IOS compilation flag introduced in #24647 and observe it fails on platforms other than iOS.

Link to public reproduction project repository

No response

Version with bug

8.0.82 SR8.2

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Android, Windows

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Child view Measure Invalidated is not getting triggered. (#20722), similarity score: 0.75
• [WinUI] Cannot invalidate measure and arrange for a ContentView (#17367), similarity score: 0.71

Closed similar issues:

• InvalidateMeasure in child triggers parent measure (#3831), similarity score: 0.70
• VisualElement.InvalidateMeasure not work at Android after update VisualStudio to 17.3.0 preview2 (#8270), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[ninachen03]

Could you provide us with a sample project so we can investigate it further? Looking forward to your reply!

[albyrock87]

@ninachen03 I've been asked to file this issue here: https://github.com/dotnet/maui/pull/24647/files#r1749332288

The second ZIP here contains a sample which generated this situation :)