Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#4,377 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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
派生
179
平均合并
1 天 23 小时
30 天内合并 PR
34

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/fluentui-react-native 的其他 Issue

查看 microsoft/fluentui-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。