Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Components: Add popup-family transactions and owner-relative focus restoration

オープン
  • 何か問題がありますか？
#4,377 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
8/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
react-native, typescript
領域
desktop, frontend

調査の方向性

The work spans native presentation focus, close and restoration logic across macOS (Paper/Fabric) and Windows/Win32, plus the MenuComposition story as a prerequisite demo; start from the shared native-core contract and the historical handoff file referenced in the issue (b55d6c9a3:packages/agentic/native-core/plans/modernization.md). Done means the family-close, restoration and Tab-continuation transactions are implemented and tested for close/reopen, owner loss, nested input, Escape and races, with capability evidence recorded per host. Coordinate with #4232 and #4236 before touching Menu or Popover behavior.

索引モデルが issue の本文から書いたものです。

説明

Goal

Implement the shared native policy needed beyond a flat nonmodal Callout/Menu composition. Part of #4274. Actual Menu and Popover delivery remains #4232 and #4236; do not duplicate those component-generation issues.

Observed baseline — 2026-10-15

The initial native-core milestone confirms individual presentation focus/close/reposition and owner-window retained-focus return. It does not provide family closure, policy-driven restoration, natural owner-relative Tab continuation, request-only veto, or precise light-dismiss classification. The MenuComposition story is a prerequisite demonstration, not a shipped Menu/Popover component.

Acceptance

  • Review the shared contract for family membership/attachment generations, child/sibling/ancestor closure, reentrant dismissal, and stale result/cleanup fencing.
  • Implement family-close/restoration transactions with one navigation owner per key and one native restoration executor. Test close/reopen, owner loss, nested popup input, Escape, and restoration races.
  • Provide natural owner-relative Tab/Shift+Tab continuation without cycling back into closing popups or restoring over a newer physical focus move.
  • Resolve disabled-but-discoverable MenuItem policy: focus eligibility, activation refusal, and accessibility-disabled state are separate axes. Integrate the reviewed choice with #4232 rather than silently changing all disabled controls.
  • Keep pointer-open focus policy explicit (platform / always / never) and retain the flat default/always trigger-restoration regressions on all qualified hosts.
  • Record macOS Paper/Fabric and Windows/Win32 capability evidence and unsupported paths; do not claim root admission from a partial host implementation.

Prior art and evidence

Historical handoff: b55d6c9a3:packages/agentic/native-core/plans/modernization.md. Candidate wave-three 5f6e7af1252bcfe087dcd1672afaa4ceb7c5efbb contains macOS family work but narrower RNW coverage and a recorded Menu run of 1 passed / 0 failed / 12 skipped. Adapt selectively under current native/Apple contracts, not as already-qualified behavior. Preserve renderer adapters as thin event/view boundaries and shared behavior independent of renderer registries.

主要言語
TypeScript
スター
1.4k
フォーク
180
平均マージ
2日 23分
マージ済み PR（30日）
33

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/fluentui-react-native のほかの issue

microsoft/fluentui-react-native の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。