hermes-agent/apps/desktop/src/components/onboarding
Brooklyn Nicholson c7ef4c192d refactor(desktop): name the overlay z-index ladder
DESIGN.md already said app-wide surfaces must not compete through ad-hoc
z-index literals, and the code disagreed: three overlapping numbering
schemes, and comments narrating the fight ("defaults to z-130, renders
UNDER the onboarding overlay (z-1300) ... bump it above with z-[1310]").
Picking a number meant reading someone else's near miss.

Name the rungs — modal, over-modal, switcher, and the boot chain — and
point the call sites at them. Every rung keeps the exact value it had, so
nothing moves; what changes is that the next overlay has a name to reach
for instead of a number to guess. Local stacking within a component stays
on plain z-10/z-20.
2026-07-27 15:48:09 -05:00
..
flow.tsx refactor(desktop): name the overlay z-index ladder 2026-07-27 15:48:09 -05:00
glyph.tsx refactor(desktop): split onboarding overlay god file into onboarding/ folder 2026-06-30 13:21:49 -05:00
index.test.tsx feat(desktop): promote Fireworks AI to #2 in onboarding provider picker (#66432) 2026-07-17 14:19:57 -04:00
index.tsx refactor(desktop): name the overlay z-index ladder 2026-07-27 15:48:09 -05:00
providers.tsx fmt(js): npm run fix on merge (#66445) 2026-07-17 18:26:36 +00:00