-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[iOS] CollectionView footer sizing when source is empty in SR5 #28971
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
[iOS] CollectionView footer sizing when source is empty in SR5 #28971
Conversation
|
Hey there @@HarishKumarSF4517! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
src/Controls/src/Core/Handlers/Items/iOS/StructuredItemsViewController.cs
Show resolved
Hide resolved
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
running tests here #28976 |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run MAUI-public |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
* Revert "[iOS] CollectionView footer sizing when source is empty in SR5 (#28971)" * - fix header/footer sizing issue * - add screenshots * - set to cv1 because behavior currently differs
Description
Fix for Issue: On iOS, the CollectionView footer width becomes larger than the screen size when the CollectionView's source is empty.
This issue has already been resolved in the main branch through a combination of the current changes and the actual fix implemented in PR #28610
To resolve this issue in SR5.1, I have now included the necessary changes from the main branch into the SR5 branch. While the main branch commit contains additional file changes, I have included only the relevant modifications required to address this specific issue in CV1.
Reference Commit (from main): 609499c
Before fix:
After fix:
Issues Fixed
Fixes #28580