ListView needs to be bounded to enable virtualization

[MikeHillberg]

ListView is intelligent about not creating more item container elements than are necessary to fill the screen (plus some caching). But that only works if it knows the bounds. If you put a ListView in something like a StackPanel or ScrollViewer, there are no bounds, and the UI virtualization is broken. This should be called out as a note in this documentation.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 9a184d49-6889-2082-f5ea-5c651f40e429
• Version Independent ID: f220e171-6cbb-aca9-6324-0c7ae55bc3aa
• Content: ListView Class (Windows.UI.Xaml.Controls) - Windows UWP applications
• Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.ui.xaml.controls.listview.yml&version=GBlive&_a=contents
• Product: uwp
• Technology: winrt-reference
• Git Login: jwmsft
• Microsoft Alias: jimwalk

[Karl-Bridge-Microsoft]

Hi @MikeHillberg - Thanks for taking the time to let us know about this issue and we sincerely apologize for the delayed response.

This topic contains a link to the https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/optimize-gridview-and-listview topic, which seems to address your concern in some depth.

Does this address your issue adequately?

[HO-COOH]

Just searched about this topic, and I think that's not clear enough. The doc only mentioned about ItemsPanel, but I think what OP means is that the container of the whole ListView should have size limit. If you do something like this

<Page>
    <StackPanel>
        <ListView .../>
    </StackPanel>
</Page>

then there will be no virtualization.