We're having the same issue. In our case to make the TabView unreactive is a stack layout embedded in a scroll view inside a TabView. No other scrollable items in the view. This means that we're not able to scroll vertically the tab view content. Meanwhile this bug is fixed, can you please provide a workaround that provide scrolling?
ScrollView objects should not be nested. In addition, ScrollView objects should not be nested with other controls that provide scrolling, such as CollectionView, ListView, and WebView.
So nesting CollectionView in a ScrollView breaks the UI virtualization. And setting a definitive height was suggested to enable the swipe and reorder features.
The issue is escalated to the team, so when there is an update, the item status will be changed.
Applying that approach setting a definitive height to the CollectionView when is inside a ScrollView that is in a TabView gets in the same result of freezing when scrolling.
ADMIN
Didi
Posted on:21 Dec 2024 11:38
Hello Andy,
If you place the CollectionView in a ScrollView then set a definitive height to the CollectionView control. Test this approach in a combination with swipe and reorder feature.
Nest CollectionView into a ScrollView, this will make the CollectionView use the scroll ability from ScrollView and not itself which is the one is wrong. Of course this is not a perfect approach but worked in my case.
The bad news is that using a ScrollView, the CollectionView control can't have scroll features like Swipe and I think Drag N Drop. For my app I'm using swipe and I had to disable swipe feature from CollectionView, otherwise ScrollView's scroll won't work. To keep swipe working meanwhile Telerik solve this bug, I used a SwipeView for my item template and it is working.
Zelin
Posted on:19 Dec 2024 00:21
The Telerik team is deprecating the RadListView: Link. Perhaps we should wait for it to be fixed. From my experience, the performance of using RadCollectionView is significantly better than that of RadListView.
Andy
Posted on:18 Dec 2024 23:50
I'm experiencing the same problem and couldn't find a solution or workaround so far. ListView was working better than this.