You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a CollectionView in a MAUI application, there is an issue where the Header and Footer are not visible if the EmptyView is selected first. The expected behavior is that the Header and Footer should be displayed regardless of the order in which the EmptyView and header/footer options are selected.
Tap the EmptyView/EmptyViewTemplate button to navigate to the CollectionView Control Page.
Tap the Options toolbar item to navigate to the Options Page, then select EmptyView first and then select Header/footer . Observe that the Header/footer is not displayed.
Expected Behavior:
The Header and Footer should be visible along with the EmptyView.
Actual Behavior:
The Header and Footer are not visible when the EmptyView is selected first. However, if the Header and Footer are selected first and then the EmptyView is selected, the header and footer are displayed correctly
Description
When using a CollectionView in a MAUI application, there is an issue where the Header and Footer are not visible if the EmptyView is selected first. The expected behavior is that the Header and Footer should be displayed regardless of the order in which the EmptyView and header/footer options are selected.
Screen.Recording.2025-03-12.at.6.23.03.PM.mov
Steps to Reproduce
Expected Behavior:
The Header and Footer should be visible along with the EmptyView.
Actual Behavior:
The Header and Footer are not visible when the EmptyView is selected first. However, if the Header and Footer are selected first and then the EmptyView is selected, the header and footer are displayed correctly
Link to public reproduction project repository
No response
Version with bug
9.0.40 SR4
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
No response
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output