2026 Remote Mac Frontend Release Acceptance:
CSS Stacking Context & :has() — Safari vs Chromium Contrast Table + Three-Step Progressive Enhancement
Audience: front-end teams shipping dual-engine CSS where :has() toggles chrome and stacking contexts decide taps. Linux CI misses WebKit paint order on Apple GPUs. You get a selector matrix, stacking versus containing-block gaps, remote Safari steps, :where fallbacks plus a test table, an executable checklist, and a three-step gate. See dialog stacking, real-device Safari flows, and color-mix checklist.
Why stacking and :has() stall sign-off
1) A single transform, filter, or opacity below one on a parent creates a new stacking context that reorders children versus what your flat z-index spreadsheet assumed.
2) :has() can toggle position or overflow on ancestors, which suddenly changes the containing block for position: fixed descendants in ways Chromium Devtools previews miss until WebKit paints the page.
3) Without a remote Mac capture, PMs merge on green screenshots that hide popover bleed-through, sticky header overlap, and modal underlay bugs that only appear once real users scroll on Safari.
01 Selector support matrix
Use this matrix in design review to tag progressive enhancement versus hard fallbacks on older Safari fleets.
| Selector or feature | Safari WebKit | Chromium | Release note |
|---|---|---|---|
:has() |
Recent macOS broad; stress large DOMs. | Fast; verify shadow boundaries. | Gate with @supports selector(:has(*)). |
:where() |
Stable resets with @layer. |
Stable; watch third-party order. | Wrap resets so :has() wins cleanly. |
isolation: isolate |
Predictable modal sub-stacks. | Match; test blend modes. | Apply before tuning z-index. |
02 Stacking and containing-block interaction gaps
Log each row on a remote Mac at the same width and DPR as your top segment.
| Interaction | Safari WebKit | Chromium |
|---|---|---|
filter on hover |
Promotes stacks; popovers may slip under siblings. | Similar; retest without will-change. |
:has(:focus-visible) menus |
Hover can linger after focus moves. | Slow pointer moves expose gaps. |
fixed inside transformed parent |
Anchors to transformed box when :has() toggles transform. |
Same spec; easy to miss in review. |
On failure, attach a short clip plus the computed ancestor chain.
03 Remote Safari real-device verification steps
Run on a leased remote Mac so WebKit matches customer silicon.
- Pin builds. Paste Safari and macOS versions from About into the ticket.
- Baseline routes. Home, checkout, and one heavy dashboard at desktop and tablet widths.
- Exercise :has(). Toggle each relational menu via pointer, keyboard, and VoiceOver when applicable.
- Paint audit. In Web Inspector, name the ancestor that owns the bad stacking context.
- Archive. Upload clip plus computed
z-indexdiff versus tokens; add HAR if network-bound.
04 Fallback strategy (:where, etc.) and test case table
Wrap resets in :where() so :has() wins without !important. Add a body kill switch when marketing injects legacy CSS.
:where(.reset) :focus-visible { outline-offset: 2px; }
@supports selector(:has(*)) {
.nav:has(.mega:hover) { overflow: visible; }
}
| Test case | Expected | Safari note | Chromium note |
|---|---|---|---|
| Hover mega menu while modal open | Menu stays above dimmer; focus trap intact. | Check inert on siblings. |
Compare without isolation. |
| Keyboard close clears :has state | No ghost hover background. | Watch focus-visible versus hover. | Throttle CPU four times. |
| Fixed toast over transformed hero | Toast follows spec for containing block. | Toggle hero transform. |
Log containing block in Layers. |
05 Three-step progressive enhancement acceptance
Merge rules map to three gates.
- Probe. Log
CSS.supportsfor:has; tier surfaces as modern, reduced-motion safe, or legacy. - Matrix. Run both tables on staging; block on any P0 mismatch.
- Rollback. Ship kill-switch owner plus signed test table.
06 Executable test checklist
Paste into pull requests for reviewers.
@supports selector(:has(*))matches the branch users hit.- List ancestors with
transform,filter, lowopacity, orisolationon the surface. - Safari and Chromium layer border shots for the bad popover.
- Re-check
fixedafter toggling:has()per the table. - Repeat under Reduce Motion and Increase Contrast.
Each stacking ticket needs the smallest DOM subtree that reproduces paint order.
:has() that toggles overflow or transform is a breaking change until dual-engine sign-off.
07 FAQ
Does Chromium passing :has() mean Safari is safe?
No. Shadow DOM and compositing diverge; capture WebKit on a remote Mac.
Why wrap utility resets in :where?
Zero specificity keeps layers predictable when product adds more :has() later.
Rent or Buy a Remote Mac for Safari Stacking QA
Stop guessing paint order from Linux CI alone. Visit macwww.com for the public pricing page, help center SSH and VNC guides, and purchase or rent a remote Mac for same-day WebKit sessions. Start from the product home, compare plans on pricing, then open help before checkout.