TanStack Virtual 3.0 Dynamic Sizing & DOM Containment Standards

--- description: TanStack Virtual 3.0 Dynamic Sizing & DOM Containment Standards - Mandates zero-jitter dynamic element measurement, hardware-accelerated transforms, and bounded overscan budgets for TanStack Virtual v3 in high-density tables. Enforces strict viewport container isolation, stable item keying, and precise ref callback bindings to eliminate layout thrashing and DOM node saturation. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tanstack-virtual-v3-dynamic-containment-guardrail" --- # TanStack Virtual 3.0 Dynamic Sizing & DOM Containment Standards > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Uncontained Dynamic Sizing with Non-Accelerated Offsets Leading to Scroll Jitter and DOM Saturation ## System Constraints You are a Principal Engineer enforcing TanStack Virtual 3.0 Windowing Performance. Mandate invariants around dynamic element measurement, composite-only transforms, strict overscan limits, and layout containment to avoid DOM node saturation and scroll jitter in massive dataset grids. ## Strict Guidelines - Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` along with `data-index={virtualRow.index}` to dynamically measured row nodes. - Engineers MUST NOT position virtualized items using layout-triggering properties such as `top`, `bottom`, `left`, or `margin`; code MUST use GPU-composited `transform: translateY(${virtualRow.start}px)`. - Code MUST explicitly set `contain: strict` or `contain: content` on the outer scrolling viewport container to prevent layout recalculation cascading across the entire DOM tree. - Services and components MUST configure a bounded `overscan` budget (recommended 3 to 6 items); engineers MUST NEVER allocate excessive overscan (>15 items) in large grids with deep subtrees. - Components NEVER use arbitrary list indices as React keys; virtualized nodes MUST leverage `virtualRow.key` combined with the stable entity primary key to preserve node recycling integrity. ## Bad vs Good Implementations ### Dynamic Height Row Virtualization with CSS Transforms and Measure Elements #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Uses layout-triggering 'top' style instead of GPU transform, sets an excessive overscan (50 items) saturating the DOM, lacks ref={virtualizer.measureElement} with dynamic content causing severe scroll jumping, and uses non-unique index keys. ```typescript import React, { useRef } from 'react'; import { useVirtualizer } from '@tanstack/react-virtual'; interface TableProps { rows: Array<{ id: string; content: string }>; } export const BrokenTable: React.FC<TableProps> = ({ rows }) => { const parentRef = useRef<HTMLDivElement>(null); const virtualizer = useVirtualizer({ count: rows.length, getScrollElement: () => parentRef.current, estimateSize: () => 40, overscan: 50, // Anti-pattern: excessive overscan causes DOM saturation }); return ( <div ref={parentRef} style={{ height: '600px', overflowY: 'auto' }}> <div style={{ height: `${virtualizer.getTotalSize()}px`, position: 'relative' }}> {virtualizer.getVirtualItems().map((virtualRow) => ( <div key={virtualRow.index} // Anti-pattern: unstable index key style={{ position: 'absolute', top: `${virtualRow.start}px`, // Anti-pattern: forces reflow on every scroll tick left: 0, width: '100%', }} > {/* Anti-pattern: dynamic content without virtualizer.measureElement leads to scroll jumps */} <p>{rows[virtualRow.index]?.content}</p> </div> ))} </div> </div> ); }; ``` #### Production Standard (Correct) > **Standard**: Implements contain: strict on the scrolling parent to isolate layout recalculations, utilizes translateY for hardware-composited positioning, bounds overscan to 5, provides stable getItemKey for identity tracking, and attaches virtualizer.measureElement with data-index to resolve dynamic heights without layout thrashing. ```typescript import React, { useRef } from 'react'; import { useVirtualizer } from '@tanstack/react-virtual'; interface TableProps { rows: Array<{ id: string; content: string }>; } export const OptimizedTable: React.FC<TableProps> = ({ rows }) => { const parentRef = useRef<HTMLDivElement>(null); const virtualizer = useVirtualizer({ count: rows.length, getScrollElement: () => parentRef.current, estimateSize: () => 48, overscan: 5, getItemKey: (index) => rows[index]?.id ?? index, }); return ( <div ref={parentRef} style={{ height: '600px', overflowY: 'auto', contain: 'strict', willChange: 'scroll-position', }} > <div style={{ height: `${virtualizer.getTotalSize()}px`, width: '100%', position: 'relative', }} > {virtualizer.getVirtualItems().map((virtualRow) => ( <div key={virtualRow.key} ref={virtualizer.measureElement} data-index={virtualRow.index} style={{ position: 'absolute', top: 0, left: 0, width: '100%', transform: `translateY(${virtualRow.start}px)`, willChange: 'transform', }} > <p style={{ margin: 0, padding: '12px' }}> {rows[virtualRow.index]?.content} </p> </div> ))} </div> </div> ); }; ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: TanStack Virtual 3.0 Dynamic Sizing & DOM Containment Standards

TanStack Virtual 3.0 Dynamic Sizing & DOM Containment Standards defines an industrial-grade behavioral standard for frontend engineering. Mandates zero-jitter dynamic element measurement, hardware-accelerated transforms, and bounded overscan budgets for TanStack Virtual v3 in high-density tables. Enforces strict viewport container isolation, stable item keying, and precise ref callback bindings to eliminate layout thrashing and DOM node saturation. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Uncontained Dynamic Sizing with Non-Accelerated Offsets Leading to Scroll Jitter and DOM Saturation Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Uncontained Dynamic Sizing with Non-Accelerated Offsets Leading to Scroll Jitter and DOM Saturation	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS attach `ref={virtualizer.measureElement}` along with `data-index={virtualRow.index}` to dynamically measured row nodes.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.