Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Components: Provide modal focus scope and background accessibility isolation

Aperta
  • Qualcosa non va?
#4,379 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react-native, typescript
Ambito
accessibility, desktop-dev

Direzione di ricerca

This is design work, so start by reading the durable boundaries the issue names: the native-core README and AGENTS files, and the modern Callout and FocusZone SPEC.md files. Confirm how FocusZone navigation differs from the modal contract the issue asks for. Done means the five acceptance items are covered: modal focus containment, background isolation with idempotent teardown, the listed focus and restoration tests, a recorded platform qualification matrix, and gated root admission. Coordinate with the maintainers on #4222, #4223 and #4236 before writing code.

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

Descrizione

Goal

Establish the native modal foundation needed by Dialog #4222, Drawer #4223, and modal Popover policy in #4236. Part of #4274. Existing component-generation issues remain the delivery owners; this issue owns their shared native prerequisite.

Acceptance

  • Review host/window ownership, arbitrary-child focus containment, initial focus, Escape/close, nested modality, and safe restoration as a modal contract distinct from FocusZone navigation.
  • Implement actual background accessibility isolation and scrim/input containment with attachment/window/generation-scoped ownership and idempotent teardown.
  • Test forward/backward Tab, programmatic and assistive-technology focus escape, nested popup ownership, owner loss/unmount, close/reopen races, and restoring only when policy still permits it.
  • Qualify native keyboard and assistive-technology behavior across the declared macOS Paper/Fabric, Windows, and Win32 capability matrix; record refusals/unsupported paths explicitly.
  • Keep root/all-host admission gated by equivalent mandatory semantics; cycling a FocusZone or showing an anchored Callout is not modal qualification.

Evidence

Retired handoff: b55d6c9a3:packages/agentic/native-core/plans/modernization.md. Durable boundaries: native-core README/AGENTS and modern Callout/FocusZone SPEC.md files. Reuse proven host services without introducing a global view-tag registry or speculative cross-platform framework.

Lingua principale
TypeScript
Stelle
1.4k
Fork
179
Merge medio
2g 23m
PR unite (30g)
33

Preparare l'ambiente

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 microsoft/fluentui-react-native

Tutte le issue di microsoft/fluentui-react-native

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.