All Production Symptoms
Production Symptom4 Causal Mechanisms

My z-index: 9999 is ignored behind a sticky header

A parent with transform, opacity < 1, will-change, or filter creates an isolated stacking context that traps child z-index values inside its subtree.

DevTools / RUM Signature
Computed z-index: 9999, yet element paints underneath sibling with z-index: 10 (isolated stacking context via transform/opacity/filter)

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

Hierarchical tree isolating Z-axis paint order. A high z-index remains trapped inside its parent stacking context.

Step 2
Rendering PipelineBaseline · Widely

Promotion of a DOM subtree to a dedicated GPU texture allowing the Compositor Thread to animate transform and opacity without Layout or Paint.

Step 3
DOM & EventsSuperseded

Legacy pattern reparenting overlays to document.body via createPortal and global z-index scales—now superseded by native Browser Top Layer primitives.

Step 4
DOM & EventsBaseline · Widely

End z-index: 99999 wars and overflow: hidden modal clipping—the Browser Top Layer paints <dialog> and [popover] in a document-level LIFO list above the root stacking context.

Seen in Architecture Autopsies