CollectionView is positioned incorrectly and the scrolling is broken #6784
Labels
area-controls-collectionview
CollectionView, CarouselView, IndicatorView
platform/android 🤖
platform/windows 🪟
s/verified
Verified / Reproducible Issue ready for Engineering Triage
t/bug
Something isn't working
Milestone
Description
CollectionView behaves differently than ListView in MAUI - it is positioned incorrectly and the scrolling does not work.
I have made a sample repro project with a page that has a label on the top, followed by a CollectionView and there is another label on the bottom. This page is not rendered correctly. The label on the bottom is not visible. Moreover, only first items are shown in the CollectionView, which cannot be scrolled down to show the rest of the items.
There is another page in the repro project that uses a ListView instead of CollectionView. This page is displayed correctly.
ListView (displayed correctly, the red label on the bottom is visible):

CollectionView (displayed incorrectly, it covers the red label and it cannot be scrolled)

Moreover, the CollectionView page rendering is extremely slow (and the CollectionView has only 100 items). This is especially striking when you are on the ListView page in the repro project and then you select the CollectionView page from the flyout menu.
Steps to Reproduce
Version with bug
Release Candidate 2 (current)
Last version that worked well
Unknown/Other
Affected platforms
Android, Windows, I was not able test on other platforms
Affected platform versions
Android 10 emulator, Windows 10
Did you find any workaround?
Use a ListView instead of CollectionView if you do not need functions specific to CollectionView. Otherwise, there is no workaround.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: