CollectionView Items display issue when Header is resized on iOS#21812
CollectionView Items display issue when Header is resized on iOS#21812rmarinho merged 2 commits intodotnet:mainfrom
Conversation
src/Controls/src/Core/Handlers/Items/iOS/StructuredItemsViewController.cs
Outdated
Show resolved
Hide resolved
src/Controls/src/Core/Handlers/Items/iOS/StructuredItemsViewController.cs
Outdated
Show resolved
Hide resolved
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
mattleibow
left a comment
There was a problem hiding this comment.
I am just wondering about the fact that now we have 2 events that are triggering the layout code when the first did not work. Is there a reason for both?
| if (_headerUIView is MauiView hv) | ||
| { | ||
| hv.LayoutChanged -= HeaderViewLayoutChanged; | ||
| } |
There was a problem hiding this comment.
If we are now watching the actual method that is doing layout, do we still need the original _footerViewFormsElement.MeasureInvalidated? The code seems to end up calling the same HandleFormsElementMeasureInvalidated method.
There was a problem hiding this comment.
IS grabbing the element for footer and header not the all view right? some still need for each one .
| } | ||
|
|
||
| CrossPlatformArrange(bounds); | ||
| OnLayoutChanged(); |
There was a problem hiding this comment.
Maybe this should be renamed to match the method. Also, no need to have the method, just invoke the event directly. Maybe use a name of ArrangingSubviews or even just OnLayoutSubviews since it is internal. I see MovedToWindow got away with the same name because it was an explicit interface member.
There was a problem hiding this comment.
I changed it to invoke the event directly
|
/rebase |
e8da440 to
718e416
Compare
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@kubaflo Could you rebase and fix the conflicts? Thanks in advance. |
|
@rmarinho it turned out that I had to make some changes to fix it. So, it is not only a UI test now |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Seems is failing for CV2 |
|
@rmarinho Luckily, it is only because the iOS screenshot needs to be updated. Could you please /azp? |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
rmarinho
left a comment
There was a problem hiding this comment.
Seems the tests are failing for CV2 HeaderShouldNotCollapseWithItems
|
@rmarinho hmm, locally it works well with the following change: Maybe let's try run tests again |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
|
@rmarinho so this is actually not working on CV2. I will try to get to the bottom of why it doesn't work. But in the meantime can we merge this fix for cv1? |
|
@rmarinho I've added |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/backport to release/9.0.1xx-sr3 |
|
Started backporting to release/9.0.1xx-sr3: https://github.com/dotnet/maui/actions/runs/12911585074 |


Issues Fixed
Fixes #20538
Fixes #12429
Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-04-13.at.17.21.10.mp4
Simulator.Screen.Recording.-.iPhone.15.Pro.Max.-.2024-04-13.at.17.17.05.mp4