All Production Symptoms
Production Symptom5 Causal Mechanisms

100% of unit tests pass in JSDOM while mobile dropdown fails in prod

JSDOM stubs layout geometry, passive touch listeners, and compositor hit-testing, masking real browser failures until tested in an actual engine.

DevTools / RUM Signature
Vitest/Jest JSDOM suite green; Safari/Chrome mobile throws Unable to preventDefault inside passive event listener or misses hit-testing

Causal Chain of Browser Mechanisms

Ordered from trigger to root invariant. Open any mechanism to inspect its internals or reproduce the behavior in an interactive lab.

Step 1
Rendering PipelineBaseline · Widely

Cut layout thrashing and oversized DOM reflow costs—the Render Tree prunes display: none subtrees before Layout computes exact box geometry.

Step 2
DOM & EventsBaseline · Widely

Eliminate 100ms+ mobile scroll-start jank—{ passive: true } promises the GPU compositor thread that wheel/touch listeners will never call preventDefault().

Step 3
Testing & VerificationBaseline · Widely

Green JSDOM tests ship broken layouts because Node.js DOM shims lack a layout engine, returning zeros for geometry and ignoring stacking contexts and CORS.

Step 4
Testing & VerificationBaseline · Widely

Real setTimeout calls in tests bake CI CPU jitter into assertions; fake timers replace wall-clock APIs with a deterministic queue that still breaks if microtasks are not drained.

Step 5
Testing & VerificationBaseline · Widely

CSS and data-testid selectors pass on clickable divs that screen readers and keyboards cannot reach; querying by computed ARIA role and accessible name tests the user-facing contract.

Seen in Architecture Autopsies