If EndItemSwipe() is called inside the ItemSwiping event handler, the ItemSwiping event continues to occur on iOS until the user physically ends the swipe gesture.
This can be reproduced in the SDK examples ->ListView -> Gestures -> CellSwipeEvents. 1. Change the content of the items so that they have uneven height 2. Scroll down 3. Delete an item by swiping -> Expected result : The items re-arrange correctly -> Actual result : The item is deleted but the ListView is scrolled up when the UI is updated
When LoadOnDemand event have loaded its data then there is some kind of jumping down through the new items while scrolling.
The LoadOnDemandItemTemplate's HorizontalOptions setting is ignored on Android, it will always be left aligned. See this screenshot for comparison of 3 target platforms side-by-side: https://www.screencast.com/t/K5oWBcP0dLQM The DataTemplate is as follows: <telerikDataControls:RadListView.LoadOnDemandItemTemplate> <DataTemplate> <Grid BackgroundColor="Red" HorizontalOptions="End"> <Label FontSize="24" HorizontalOptions="End" Text="Load more items" TextColor="Black" /> </Grid> </DataTemplate> </telerikDataControls:RadListView.LoadOnDemandItemTemplate>
Follow this tutorial https://docs.telerik.com/devtools/xamarin/controls/listview/listview-features-load-on-demand#loading-mode-with-collection
It works on Android and iOS, but on UWP it is defaulting to Explicit mode and clicking the load button crashes the app.
When RadListView is setup to load its items on demand and the LayoutDefinition is GridLayout with SpanCount set to 2 or more, the Footer Template does not take all the width, it expands only to the Width of the first column.
Currently groupheader can be stretched by using GroupHeaderLength property instead rather than resolving it automatically.
The following exception is thrown when scrolling ListView with Grid layout with many columns and rows: Windows.UI.Xaml.LayoutCycleException: Layout cycle detected. Layout could not complete.
The bug can be reproduced on iOS 13 only. It is not reproducible on earlier versions of iOS. Run the attached project on iOS 13 device or Simulator to reproduce it.
Sometimes when focusing an entry and the onscreen keyboard shows up, the ListView is not scrolled correctly, so the entry is overlapped by the keyboard. The ListView layout appears messed up after that and the scrolling does not behave correctly.
Activating the ItemHold event of an item in a list view requires holding down an item for a while. On a physical/virtual Android device and a virtual iOS device, this can be done by holding down the mouse/finger lightly on an item for a short period of time. However, on a physical iOS device (I am using a physical iPhone 6s to test this), holding down the item lightly with my finger won't activate the ItemHold event, and I have to hold the item really hard on the screen in order to activate it (similar to using 3D Touch / Force Touch, and I cannot reliably activate the ItemHold event possibly because my force is sometimes not hard enough). I noticed this behaviour on the physical iOS device since the ItemHold event got implemented in early 2018.
I created a simple application to demonstrate the issue. The app displays an alert when the user taps/holds an item in the list view. On a physical iOS device, holding down an item in the list view requires the user to press the item very hard on the screen.