Components: Provide modal focus scope and background accessibility isolation
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react-native, typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- TypeScript
- 星标
- 1.4k
- 派生
- 180
- 平均合并
- 2 天 23 分钟
- 30 天内合并 PR
- 33
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/fluentui-react-native 的其他 Issue
-
MenuList: FocusZone not wired for react-native-windows ('windows'), so menu items are Tab-only (no arrow-key roving focus)可能已有人在做 @UditDewan 于 3 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
microsoft/fluentui-react-native#4174 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 24/100
microsoft/fluentui-react-native#4384 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 32/100
microsoft/fluentui-react-native#4383 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 12/100
microsoft/fluentui-react-native#4380 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 5/100
microsoft/fluentui-react-native#4378 ·
维护者通常 1 天内回复
查看 microsoft/fluentui-react-native 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 65/100
521xueweihan/HelloGitHub#4025 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
voidzero-dev/void#478 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 69/100
Small-tailqwq/dsh-deep-whale#207 ·
维护者通常 1 天内回复
-
The inspector never shows the instances field, so scaling out is unreachable可能已有人在做 @Mrkewl 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
xevrion/breakscale#96 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
Flux159/mcp-server-kubernetes#384 ·