when a new ObservableCollection is assigned to the listview's ItemsSource during load on demand, there is an inconsistency in the scrolling.
- On Android the listview is scrolled to the top immediately and showing items at the top of the listview.
-On iOS and UWP, the listview position is not changed.
When reordering items in the ListView sometimes the user might want the item to go to the end of a long list. It is not possible, because the ListView does not scroll while dragging the item.
When RadListView is placed inside Grid with ColumnDefinition with Height="Auto", setting FlowDirection to "RightToLeft" raises an exception.
It seems the scroll position is calculated incorrectly in this case.
When you drag an item and want to drop it after the visible items the ListView should auto scroll. This works with a vertical orientation.
When an item in the ItemsSource of a ListView is null, a NullReferenceException will be raised on Android when the items source is loaded to the list view. Even if a DataTemplateSelector is applied to display a different datatemplate for null items, the app would still crash.
I attached a sample program that demonstrates the issue. On iOS the app runs fine, but on Android the app crash at launch with a NullReferenceException.
Thanks,
Kori
When using load on demand mode manual, and collapsing groups, one item left not collapsed.