# Native browser virtual scroller

**URL:** <https://meta.discourse.org/t/native-browser-virtual-scroller/116143>\
**Category:** Development\
**Created:** [April 27, 2019, 10:06pm UTC](https://meta.discourse.org/t/native-browser-virtual-scroller/116143 "2019-04-27T22:06:17Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![dfabulich](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dfabulich/32/108716_2.png) [@dfabulich](https://meta.discourse.org/u/dfabulich)\
**Post date:** [April 27, 2019, 10:06pm UTC](https://meta.discourse.org/t/native-browser-virtual-scroller/116143/1 "2019-04-27T22:06:18Z")

</div>

Browsers are beginning to form a standard around browser-native virtual scrolling.

[[GitHub - WICG/virtual-scroller · GitHub](https://github.com/WICG/virtual-scroller)]

> A built-in virtual scroller for the web platform

[![](https://global.discourse-cdn.com/meta/original/4X/d/d/1/dd1aef0ccff64f70a074f3c781449a9d7a41624b.jpeg "virtual-scroller: Let there be less (DOM) (Chrome Dev Summit 2018)") ](https://www.youtube.com/watch?v=UtD41bn6kJ0)

They’re also exploring some really interesting low-level browser APIs that would allow find-in-page and a11y navigation for large volumes of invisible content.

[[GitHub - rakina/find-in-page-api · GitHub](https://github.com/rakina/find-in-page-api)]

> There have been a lot of interest in improving the find-in-page experience from web developers, including:
> 
> - Giving the user a completely custom UI, suppressing the browser’s find UI, consistently
> - Allowing data not in the DOM tree to be findable, even if there might be an infinite amount of data
> - Reflecting real-time data loading/modification on find results
> - Treating multiple webpages as one searchable instance, e.g. books, multi-page articles, or the multipage HTML spec

[[GitHub - rakina/searchable-invisible-dom · GitHub](https://github.com/rakina/searchable-invisible-dom)]

> The proposal is to create some new way of exposing DOM to the browser, that is still _searchable_, but is _invisible_. That is, find in page must be able to search within this DOM and fragment navigation should be able to find a named invisible DOM, etc., but we shouldn’t need to do all the work of layout/paint/etc.

[[GitHub - WICG/display-locking: A repository for the Display Locking spec · GitHub](https://github.com/WICG/display-locking)]

> This document proposes to augment user-agent APIs to help address the problem of **slow rendering phase updates** , and having some control on **when to pay rendering costs**. Specifically, we propose a concept of _display locking_ an element.
> 
> If an element is display locked, it means that **any DOM, style or layout updates to its subtree are not rendered immediately**. Instead, when allowed, the user agent will process rendering updates _co-operatively_, yielding periodically to allow script or user interactions to happen. The web author can also commit the lock, which triggers a synchronous update and render when necessary, causing the element to get updated and rendered in the next frame.
> 
> The web author can also opt-in to allow display-locked elements to be **committed by the user agent in cases like focus navigation, find-in-page match navigation** , etc. so that they are properly rendered when needed in those cases.

Stuff like this seems highly relevant to the implementation of Discourse.

---

_[View the full topic](https://meta.discourse.org/t/native-browser-virtual-scroller/116143)._
