A crashed modal: how does a mouse user get out?

Click-outside no longer closes a dialog (24 Oct 2026). When a modal’s content crashes, the boundary replaces it, buttons and all, with the broken mark. Export, Feedback, Miro and FigJam have nothing outside that boundary, so the backdrop click was the only mouse exit.

artefact: shipped CSS and stringscommentary: not the product
before Export, working
1 Mark + the dialog’s Close
2 Shell ✕chosen 24 Oct 2026
3 Mark only
Commentary

before — Export, working

For reference: the dialog the three crashed frames stand in for. Its Cancel lives inside the crashable part.

1 — Mark + the dialog’s Close

The boundary’s modal fallback adds one button, buttons.close, in the dialog’s own action row. No new words. It qualifies the “no button” rule only inside a modal, where the rest of the report is blocked and the mark can’t be “ignored if the rest works”. Matches the native sheet, which always has a button out and no ✕.

2 — Shell ✕ (chosen 24 Oct 2026)

The ✕ Settings already has, moved onto every modal’s shell, outside the boundary. Always there, crash or not. It settles the open ✕ question as “keep it”, against the native sheet, and doubles every working dialog’s Cancel.

3 — Mark only

As shipped today minus the backdrop click. Esc closes it; ⌘R or View ▸ Reload Report reloads. A mouse-only researcher who doesn’t know either is stuck behind a blocked report until they find the reload.

Not shown

The scrim and radius are today’s (black 50%, 8 pt). The measured macOS sheet look (grey 170 at 59%, ≈20 pt, a 32 pt drop) is a separate change, planned with the shared dialog.