Win32: Track popup-host continuation, lifecycle, and accessibility capabilities
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 24/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- react-native, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
onShowas attached/positioned readiness and the ordering ofsetInitialFocus/RCTFocusTrapZonefocus 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
/legacysignatures/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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 1.4k
- Forks
- 179
- Merge medio
- 2 d 23 min
- PR fusionados (30 d)
- 33
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/fluentui-react-native
-
MenuList: FocusZone not wired for react-native-windows ('windows'), so menu items are Tab-only (no arrow-key roving focus)Posiblemente ocupada @UditDewan la tomó hace 2 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
microsoft/fluentui-react-native#4174 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 32/100
microsoft/fluentui-react-native#4383 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 12/100
microsoft/fluentui-react-native#4380 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 18/100
microsoft/fluentui-react-native#4379 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 5/100
microsoft/fluentui-react-native#4378 ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/fluentui-react-native
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
anomalyco/opencode#56380 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
BUG | `MCP 服务器` | 全局层行的停用/启用与删除报 404 server row not found，编辑保存会在 profile 层复制出重复行Posiblemente ocupada @w6242652 la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Chocobozzz/PeerTube#7832 ·
Los mantenedores suelen responder en 3 días
-
Pay to use?Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 66/100
darkreader/darkreader#16108 · 1 comentario ·
Los mantenedores suelen responder en 2 días