IonInfiniteScroll pagination and DOM memory management

The IonInfiniteScroll component provides a UI trigger to implement lazy loading by appending data chunks to a bound array. While the component manages the trigger state and the complete() signal, it does not natively handle the removal of off-screen elements from the DOM as the dataset grows.

In applications handling exceptionally large datasets, appending thousands of items to the DOM can lead to significant memory overhead and degraded scroll performance, regardless of the underlying framework (Angular, React, or Vue).

When integrating this component with a paginated API, there is a need to balance the ease of IonInfiniteScroll with the memory efficiency of virtualized lists.

• Does IonInfiniteScroll support a native configuration to prune old DOM nodes as new pages are appended?
• What is the recommended architectural approach to combine this trigger with a virtual scrolling strategy to prevent linear memory growth?