# Virtualization using the content-visibility CSS API

**URL:** https://discuss.codemirror.net/t/virtualization-using-the-content-visibility-css-api/9887
**Category:** v6
**Created:** [September 11, 2026, 4:28am UTC](https://discuss.codemirror.net/t/virtualization-using-the-content-visibility-css-api/9887 "2026-09-11T04:28:36Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![nimeshnayaju](https://discuss.codemirror.net/user_avatar/discuss.codemirror.net/nimeshnayaju/32/2557_2.png) [@nimeshnayaju](https://discuss.codemirror.net/u/nimeshnayaju)
#### Post date: [September 11, 2026, 4:28am UTC](https://discuss.codemirror.net/t/virtualization-using-the-content-visibility-css-api/9887/1 "2026-09-11T04:28:36Z")

</div>

Hi! Would you consider an option in `@codemirror/view` to render the entire document without JavaScript-based virtualization?

My main motivation is compatibility with browser-native features and tools that inspect the DOM. Browser extensions, including AI agents, can miss content that isn’t mounted, and browser-native “Find in page” cannot search the complete document.

I’d even be okay to sacrifice (JavaScript/CSS) virtualization completely for documents that I already know aren’t going to exceed certain number of lines or size purely to support these use cases.

In my own experiments with `content-visibility: auto`, grouping multiple lines into blocks rather than applying it to individual lines, I found that it performed reasonably well in Chrome and Firefox. Safari struggled more, though that may be specific to my implementation.