Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
ListView on UWP always work virtualization.
But ListView doesn't work virtualization when using Xamarin.Forms.
This problem was reported as bug.
In order to solve, I recommend to delete <Setter Property="MinHeight" Value="0" /> from FormsListViewItem Style (Xamarin.Forms.Platform.UAP/Resources.xaml).
Why deletion of MinHeight.
Becose virtualization ListView on UWP calculate the display range from ListViewItem's height.
And if ListViewItem's height is 0 when inserting, Virtualization ListView on UWP calculate from ListViewItem's MinHeight. ( Maybe, The height of theXamarin.Forms ListViewItem is 0 when inserting.)
In my research, ListView on UWP has strange specification as following:
1.If set ListViewItem's MinHeight by user, ListView on UWP calculate the display range from ListViewItem's MinHeight. ListView virtualization doesn't work.
2.If set ListViewItem's MinHeight by default, ListViewItem's MinHeight is 0. But The ListViewItem's Height isn't 0 When calculate the display range. ListView virtualization work.
For that reason, I recommend to delete MinHeight Setter.
# Environment Info
Visual Studio Community 2015 Update 38948
Windows 10 build 14393
*** This bug has been marked as a duplicate of bug 38948 ***