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

Win32: Track popup-host continuation, lifecycle, and accessibility capabilities

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
24/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
react-native, typescript
领域
accessibility, backend-api-design, mobile

调研方向

Read the integration contract and the A1–C3 capability backlog, then inspect issues #4236, #4232, #4231, #4224, #4377, and #4376 for context. Start by identifying the actual Win32 view-manager props, events, and commands available in the stated React Native Win32 0.81.9 / REX 0.81.1 baseline. Done requires an assigned host owner and release vehicle, verified capability metadata, and recorded physical-input and UIA evidence before each addition is enabled.

由索引模型根据 Issue 内容生成。

描述

Purpose

Track the Office/REX host capabilities needed by the Popover (#4236), Menu (#4232), MenuButton (#4231), and Dropdown (#4224) implementation plan. This is the Win32 host follow-up to #4377 and #4376, not an expansion of the stable native-core /legacy API.

Approved interim

The owner approved the Win32 interim on October 16, 2026: Tab/Shift+Tab close the popup and return to its live trigger instead of continuing past it. All four desktop endpoints still ship together. This exception does not claim owner-relative continuation and must be documented and tested explicitly. Do not synthesize a second Tab or require caller-supplied neighboring targets.

Host capability backlog

  • Add owner-relative forward/backward Tab continuation from the trigger's actual native tab position, including native Office controls, disabled/reordered stops, and active-window guards (A1).
  • Qualify onShow as attached/positioned readiness and the ordering of setInitialFocus/RCTFocusTrapZone focus events; add a native result or ordering guarantee if the existing host cannot establish them (B1/B2).
  • Qualify child-popup input, ancestor input, deepest Escape, sibling replacement, and atomic family closure; add family support where the current host fails (B3/B8).
  • Qualify restoration against later focus moves into native Office controls and trigger press-in/light-dismiss/press ordering; add guarded restoration or anchor-aware dismissal if needed (B4/B5).
  • Qualify the actual key descriptors honored by the host and native UIA menu/combobox/list selection patterns, states, operations, and cross-window ControllerFor relationships; fix missing transport/projection where needed (B6/B7).
  • Consider close/reposition acknowledgements, precise outside/deactivation dismissal causes, and live system menu-show-delay publication as enhancements (C1-C3).

B items are qualification questions, not assertions that the baked host is defective. The current baseline is React Native Win32 0.81.9 / REX 0.81.1. This repository cannot add compiled functionality to that prebuilt host.

Integration contract

  • Detect actual view-manager props/events/commands instead of sniffing product versions. Never dispatch a new managed command unless the host declares it.
  • Keep unclassified dismissal and unsupported operation results truthful; do not manufacture readiness or confirmation.
  • Preserve existing native registration names and /legacy signatures/React compatibility.
  • Record the host owner, release vehicle, capability metadata, exact build/integration result, and physical input plus intended UIA-pattern evidence before enabling each addition. Owner/release vehicle remain to be assigned.
主要语言
TypeScript
星标
1.4k
派生
180
平均合并
2 天 23 分钟
30 天内合并 PR
33

环境准备

从这里开始

  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 摘要。