Virtual List item array size limit before client-side pagination is required

Goal: Render a large collection in Framework7 Virtual List with Searchbar filtering while keeping scroll performance stable.

Virtual List reuses DOM nodes for visible rows only, but the application must supply the complete item array. Framework7 does not issue fetch requests or enforce server-side pagination. Searchbar filters the supplied array client-side, so filtering a very large array on the main thread may cause jank unless debounced or combined with virtualization.

It is unclear whether the array should be bounded before assignment, or whether pages should be fetched and replaced as the user scrolls, and how Searchbar should treat unloaded pages.

• Should the application slice the dataset into pages before assigning items to Virtual List, or pass the full array and rely on virtualization?
• When Searchbar is active, should filtering run against the complete dataset or only the currently loaded page?
• Does dynamic item height change the safe item count threshold for stable scroll offsets?