Escape inside a focused submenu closes the entire Dropdown instead of returning to its parent item

Aperta
  • Qualcosa non va?
#274 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
67/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
react, typescript
Ambito
accessibility, frontend

Direzione di ricerca

Start with src/hooks/useAccessibility.ts and trace how Escape is handled when focus is inside a nested Menu submenu. Reproduce the reported sequence in Chrome: open the Dropdown, focus Submenu, open it with ArrowRight, then press Escape. Done means the submenu closes, focus returns to its parent menuitem, and the parent Dropdown stays open without calling onOpenChange(false).

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Reproduction
import Dropdown from '@rc-component/dropdown';
import Menu from '@rc-component/menu';

<Dropdown trigger={['click']} overlay={
  <Menu items={[{ key: 'sub', label: 'Submenu', children: [
    { key: 'child', label: 'Child' },
  ] }]} />
}>
  <button>Nested actions</button>
</Dropdown>
  1. Click the trigger.
  2. Press Tab to focus Submenu.
  3. Press ArrowRight to open the submenu and focus Child.
  4. Press Escape once.

Actual: both the submenu and parent Dropdown close, onOpenChange(false) runs, and focus goes to the Dropdown trigger.

Expected: close the submenu that contains focus and return focus to its parent menuitem; leave the parent Dropdown open. This follows the Escape behavior in the APG menu pattern.

Verification and scope

Reproduced with real Chrome key presses on macOS, using the source at PR #273 head b22af69306b82d60e64c6f513956564d019fe781 and again with only src/hooks/useAccessibility.ts restored from its base b4ea62f3293851934d64d9d92cbbd07d87a40dea. Both have this behavior, so this is an existing integration problem, not a regression introduced by #273. The single-level Escape focus fix in #273 works in the same native-browser comparison.

Dependencies: React/ReactDOM 19.3.1, menu 1.6.0, trigger 3.10.1, portal 2.2.1. Dependencies were installed in an isolated checkout from declared ranges (no upstream lockfile). An independent jsdom Dropdown/Menu integration test also observes the parent-close callback in both hook versions. No screen-reader conformance claim.

Checked open/closed submenu and Escape issue/PR searches here before filing. #38 concerns old menu-v6 layout; #272/#273 concern single-level Escape focus return. No duplicate source patch opened. AI-assisted reproduction and report; the described browser actions and tests were executed locally.

Lingua principale
TypeScript
Stelle
181
Fork
112
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di react-component/dropdown

Tutte le issue di react-component/dropdown

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.