Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Components: Provide modal focus scope and background accessibility isolation

Ouverte
  • Quelque chose ne va pas ?
#4,379 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
react-native, typescript
Domaine
accessibility, desktop-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1.4k
Forks
179
Merge moyen
2 j 23 min
PR mergées (30 j)
33

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/fluentui-react-native

Toutes les issues de microsoft/fluentui-react-native

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.