TanStack Virtual 3.0 Dynamic Windowing & Scroll Containment Standard

--- description: TanStack Virtual 3.0 Dynamic Windowing & Scroll Containment Standard - Enforces strict virtualizer lifecycle management in TanStack Virtual 3.0 for massive, dynamic datasets. Prevents DOM node saturation, layout thrashing, and sub-pixel jitter by mandating accurate ref dynamic measurement callbacks, scroll margin isolation, and GPU-accelerated CSS transform positioning. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tanstack-virtual-v3-dynamic-measurement-guardrail" --- # TanStack Virtual 3.0 Dynamic Windowing & Scroll Containment Standard > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Uncontained Dynamic Row Measurements Inducing Infinite Resize Loops and Layout Thrashing ## System Constraints You are a Principal Engineer enforcing TanStack Virtual 3.0 Windowing Performance. Mandate absolute isolation of scroll containers, non-re-rendering dynamic element measurement via measureElement ref attachments, strictly transform-based translate3d rendering, and explicit overscan caps to prevent DOM saturation. ## Strict Guidelines - Engineers MUST ALWAYS attach the virtualizer `measureElement` callback directly via the dynamic DOM node's `ref` prop or `data-index` attribute to allow accurate asynchronous dimension calculation. - Engineers MUST NOT position virtualized items using CSS `top` or `margin-top`; they MUST use CSS `transform: translateY(...)` with `contain: strict` or `content-visibility: auto` to prevent reflow cascading across parent containers. - Engineers MUST calibrate `overscan` to a fixed bounded integer (typically 3 to 10 rows); overscan MUST NEVER scale proportionally with total row count or viewport dimension. - Components NEVER trigger synchronous React state updates inside dynamic measurement hooks or element ResizeObservers, as this induces unrecoverable layout thrashing and render loop deadlocks. - Scroll containers MUST declare explicit `overflow: auto` or `overflow: scroll` alongside deterministic height constraints (fixed or relative viewport units) to prevent scroll margin detachment. ## Bad vs Good Implementations ### Dynamic Height Row Virtualization with Sub-pixel Containment #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Using top-based positioning triggers continuous CSS layout reflows during scrolling. Lack of measureElement ref binding causes dynamic text to clip or overlap due to uncorrected estimate sizes. An unbounded overscan formula completely bypasses virtualization benefits on large datasets, causing DOM node saturation. ```typescript import React from 'react'; import { useVirtualizer } from '@tanstack/react-virtual'; interface TableProps { rows: Array<{ id: string; content: string }>; } export const FlawedVirtualTable: React.FC<TableProps> = ({ rows }) => { const parentRef = React.useRef<HTMLDivElement>(null); // ANTI-PATTERN: Fixed estimate size with dynamic content without measurement callback; // unbounded overscan saturating DOM; positioning via 'top' forcing parent layout recalculation. const virtualizer = useVirtualizer({ count: rows.length, getScrollElement: () => parentRef.current, estimateSize: () => 50, overscan: rows.length / 10, // Dangerous: saturates DOM at scale }); return ( <div ref={parentRef} style={{ height: '600px', overflowY: 'auto' }}> <div style={{ height: `${virtualizer.getTotalSize()}px`, position: 'relative' }}> {virtualizer.getVirtualItems().map((virtualRow) => ( <div key={virtualRow.key} style={{ position: 'absolute', top: `${virtualRow.start}px`, left: 0, width: '100%', }} > {rows[virtualRow.index].content} </div> ))} </div> </div> ); }; ``` #### Production Standard (Correct) > **Standard**: Adheres to performance invariants by attaching virtualizer.measureElement to dynamically sized DOM nodes, positioning via hardware-accelerated translateY, stabilizing keys with getItemKey, bounding overscan to 5 items, and applying contain: strict to isolate layout calculations from document reflows. ```typescript import React from 'react'; import { useVirtualizer } from '@tanstack/react-virtual'; interface TableProps { rows: Array<{ id: string; content: string }>; } export const IndustrialVirtualTable: React.FC<TableProps> = ({ rows }) => { const parentRef = React.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', }} > <div style={{ height: `${virtualizer.getTotalSize()}px`, width: '100%', position: 'relative', }} > {virtualizer.getVirtualItems().map((virtualRow) => ( <div key={virtualRow.key} data-index={virtualRow.index} ref={virtualizer.measureElement} style={{ position: 'absolute', top: 0, left: 0, width: '100%', transform: `translateY(${virtualRow.start}px)`, willChange: 'transform', }} > {rows[virtualRow.index].content} </div> ))} </div> </div> ); }; ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: TanStack Virtual 3.0 Dynamic Windowing & Scroll Containment Standard

TanStack Virtual 3.0 Dynamic Windowing & Scroll Containment Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict virtualizer lifecycle management in TanStack Virtual 3.0 for massive, dynamic datasets. Prevents DOM node saturation, layout thrashing, and sub-pixel jitter by mandating accurate ref dynamic measurement callbacks, scroll margin isolation, and GPU-accelerated CSS transform positioning. 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 Row Measurements Inducing Infinite Resize Loops and Layout Thrashing 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 Row Measurements Inducing Infinite Resize Loops and Layout Thrashing	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 the virtualizer `measureElement` callback directly via the dynamic DOM node's `ref` prop or `data-index` attribute to allow accurate asynchronous dimension calculation.

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.