CollectionView shows incorrect gaps between items. The controls snap into the correct location when scrolling begins.
Controls are laid out correctly.
Incorrect spacing between items. The controls snap into the correct location when you start to scroll the view.
When the page is loaded:
As soon as a scroll starts to happen:
https://github.com/DuncWatts/CollectionViewRepro
Specifically: https://github.com/DuncWatts/CollectionViewRepro/blob/master/CollectionViewRepro/CollectionViewRepro/MainPage.xaml
None
This happens when views have different heights inside the collectionview. This is not ok as we have a duplicate issue #7699 that is almost a year old. The collectionview should be in preview until this is fixed. New people are gonna use the collectionview and run into this bug and be really confused. @samhouts @davidortinau @jamesmontemagno
This happens when views have different heights inside the collectionview. This is not ok as we have a duplicate issue #7699 that is almost a year old. The collectionview should be in preview until this is fixed. New people are gonna use the collectionview and run into this bug and be really confused. @samhouts @davidortinau @jamesmontemagno
I have given up on the collection view and only use BindableLayouts with a scroll view. It seems to be the most consistent way of drawing content of arbitrary size that works for the most part.
@AntonIOIOIO agreed. No idea why Xamarin can't stop putting extremely buggy controls into release. Total lack of discipline in the team as far as I can tell.
Ah so it's a caching fault with multiple items sharing heights.
I've modified my example with a spacer that gives a random height between 0.0 and 0.1px for each item and that seems to be a workaround for now.
@DuncWatts what iOS version are you running on?
I tried on a few iPhone 6s's and I'm not seeing that first layout
@PureWeen I'm using a physical device running iOS 13.6
@duncanmak what device?
Ok got it to reproduce on the SE 2nd generation.
When the repo loads:
If I try to scroll it fixes the issue
Most helpful comment
@AntonIOIOIO agreed. No idea why Xamarin can't stop putting extremely buggy controls into release. Total lack of discipline in the team as far as I can tell.