Modals stay modal (page inert, scrim live) for the whole exit animation: the first click after an outside dismissal is lost
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 55/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- accessibility, frontend, testing
Direção de pesquisa
Start with components/Dialog/Dialog.svelte, primitives/presence.svelte.js, and primitives/layer.js to trace how closing state, animation completion, modal behavior, focus, and scroll locking interact. Reproduce the lost click using the provided Playwright timing steps, then inspect the ModalContract browser test mentioned in the issue. Done means a click shortly after dismissal reaches the page button and a nonterminating descendant animation cannot keep the dialog modal; the issue does not name exact test paths.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
What happens
A modal (Dialog, AlertDialog, Drawer, Sheet, CommandPalette) is closed by pressing outside it (or Escape, or a button). The user then clicks a button on the page behind it right away: the click does nothing, a second click is needed. The cursor looks stuck.
Measured on WebKit (Playwright 1.65 WebKit, headless, real mouse events; @codeatlasdev/ui 4.6.0), a click on a page button N ms after the dismissal:
| ms after dismissal | button handler runs |
|---|---|
| 30, 80 | no (press lost) |
| 150, 250, 400 | yes |
The same on Chromium (30 ms: lost). It is the whole 150 ms exit animation (--ca-enter-fast).
Root cause (installed 4.6.0, dist/)
Closing only flips data-state="closed"; the layer stays alive, still modal, until the exit animation finishes:
components/Dialog/Dialog.svelte:109,118createPresence(() => open)/{#if presence.present}: the<dialog>stays rendered whileexiting.primitives/presence.svelte.js:16-46(exiting = true, rAF, thenPromise.allSettled(anims.map(a => a.finished))at line 40):exitingonly clears when every running animation, in the whole subtree, has finished.primitives/layer.js:435-436dialog.showModal()and:460-466dialog.close()run only in the layer'sclose(), which the owner calls when the{#if}branch is destroyed, i.e. after the exit. Until then the dialog is a modal: the rest of the page is inert (HTML "blocked by a modal dialog") and::backdrop(dialog.css:51) still takes the pointer. A press on the page goes to the closing dialog:layer.js:451-456onClickcallsonDismissagain (a no-op) and the click never reaches the button.layer.js:25-35: a closing entry is skipped bytopInteractive/topModal, so the kit already treats the layer as "closing"; only the platform state (modal, inert, focus traplayer.js:434, scroll lock:432) is not released.
Side effect of the same line: an animation that never ends inside the dialog (a spinner with animation-iteration-count: infinite) makes Promise.allSettled wait forever, so the dialog never leaves (and stays modal).
Minimal reproduction
<script>
import { Dialog, Button } from "@codeatlasdev/ui";
let open = $state(false), n = $state(0);
</script>
<Button onclick={() => (open = true)}>Open</Button>
<Button id="other" onclick={() => n++}>Other {n}</Button>
<Dialog bind:open title="Dialog">hello</Dialog>
Open the dialog, press the scrim, and press #other within 150 ms (Playwright: page.mouse.click(scrim), page.waitForTimeout(30), page.mouse.click(other)): n stays 0.
Expected
A layer that has started closing must not intercept input: the page answers the first click after a dismissal, at any time.
Proposed fix
When a modal layer starts closing (closing() turns true in modalLayer), release the platform side at once and keep only the visual exit: release the focus trap and the scroll lock, dialog.close() then dialog.show() (non-modal, no ::backdrop, no inert page; re-focus the previously focused element after show() because it moves focus into the dialog) and draw the scrim fade with the dialog's own box-shadow spread, or fade a non-interactive sibling. pointer-events: none on [data-state="closed"] for the panel. Independently: in presence.svelte.js ignore animations whose effect.getComputedTiming().endTime is Infinity.
Also add a browser test (ModalContract-style): dismiss by scrim, click a page button 0/30/80 ms later, expect one handler call each.
Workaround in Atlas
codeatlasdev/atlas#501: one document-level observer finishes the exit animation of any closing dialog.ca-overlay (the kit then drops the layer the next frame), plus .ca-floating[data-state="closed"] { pointer-events: none }. Documented with the removal condition in docs/desktop.md ("UI kit workarounds"). Atlas will delete it when a kit release passes its regression test without it.
- Linguagem predominante
- TypeScript
- Estrelas
- 6
- Forks
- 3
- Merge médio
- 5h 21min
- PRs com merge (30d)
- 378
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de codeatlasdev/ui
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
codeatlasdev/ui#1340 ·
Mantenedores costumam responder em até 1 dia
-
area:a11y area:components bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
codeatlasdev/ui#1336 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
codeatlasdev/ui#1329 ·
Mantenedores costumam responder em até 1 dia
-
good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
codeatlasdev/ui#1292 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
area:components enhancement good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
codeatlasdev/ui#1198 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de codeatlasdev/ui
Issues semelhantes
-
bug frontend
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
CivicTechWR/accessible-housing-portal#578 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
nekko-labs/nekko-agent#2998 ·
Mantenedores costumam responder em até 1 dia
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskAberta
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 86/100
sandbox-quantum/switch#2163 ·
Mantenedores costumam responder em até 1 dia
-
enhancement ux
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
lolimmlost/aidj#433 ·
Mantenedores costumam responder em até 1 dia
-
test: ipcShownDialogKeys.test.tsx can fail the unit run with 'window is not defined' after it endsAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia