Items are stuck to the CollectionView when there is ItemSpacing

[hprez21]

Description

The items are stuck to the sides of the CollectionView, preventing to see the other items when there is an assignment to ItemSpacing.

Steps to Reproduce

1.- Create a new .NET MAUI project.
2.- Remove the default code.
3.- In the xaml file:

<CollectionView>
        <CollectionView.ItemsLayout>
            <LinearItemsLayout ItemSpacing="50" Orientation="Horizontal" />
        </CollectionView.ItemsLayout>
        <CollectionView.ItemsSource>
            <x:Array Type="{x:Type x:String}">
                <x:String>mono</x:String>
                <x:String>monodroid</x:String>
                <x:String>monotouch</x:String>
                <x:String>monorail</x:String>
                <x:String>monodevelop</x:String>
                <x:String>monotone</x:String>
                <x:String>monopoly</x:String>
                <x:String>monomodal</x:String>
                <x:String>mononucleosis</x:String>
            </x:Array>
        </CollectionView.ItemsSource>
        <CollectionView.ItemTemplate>
            <DataTemplate>
                <Frame Margin="5">
                    <Label Text="{Binding .}" />
                </Frame>
            </DataTemplate>
        </CollectionView.ItemTemplate>
    </CollectionView>

Scroll the collection to the right, and view the problem..

Version with bug

6.0.400 (current)

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Android 10

Did you find any workaround?

No.

Relevant log output

No response

[kristinx0211]

can see this issue on android 11, seems on android 12, it works fine.

[AswinPG]

@kristinx0211 There seems to be the same issue on android 12 too but it's not easily visible as in 11 because of the change in animation. In android 11 there is that ripple effect but on 12 instead of ripple, there is elastic effect. The scroll feels like it has reached the end but in reality it can be scrolled further... Please check :)

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.