TreeView: [iOS] Scrolling does not work properly when custom ItemTemplates with different height are used.

Progress® Telerik® UI for Xamarin Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 15 Jan 2020 12:10 by ADMIN

Release R1 2020

Martin

Created on: 10 Oct 2019 07:45

Category: TreeView

Type: Bug Report

TreeView: [iOS] Scrolling does not work properly when custom ItemTemplates with different height are used.

When you have custom ItemTemplates defined with different height, scrolling up through the items causes flickering, also you cannot scroll down to display all the items.

Duplicated Items

[iOS] TreeView scrolling issue when showing expanded items

2 comments

ADMIN

Lance | Manager Technical Support

Posted on: 06 Dec 2019 20:07

Hello Martin,

So that we can investigate this, can you please reply to the Support Ticket you have open (#1430938)? Let Yana know if she can use the same demo to replicate the issue or if she needs to make changes.

Thank you for your understanding.

Regards,
Lance | Team Lead - US DevTools Support
Progress Telerik

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items

Martin

Posted on: 06 Dec 2019 07:43

Hello, are the any news on this issue? Although this bug is still standing on "approved", it seems like if it is fixed in the latest Xamarin UI release v2019.3.1119.1 (that's the latest version in Visual Studio 2017 NuGet Manager, your release history says lastest version is v2019.3.1119.410). So, scrolling seems to work without flickering now. But a new bug occured..

When you expand and collapse a parent treeitem several times, it will happend, that child treeitems loose their height if they are higher than 44px. So a child treeitem can fall back from a height of 150px to 44px. On the next expand and collapse it will have a height of 150px again. Another thing is, other parent treeitems that have a fixed height of 44px, could have a height of 150px now. It seem like if treeview virtualization is still broken. Can you approve this?