palantir/blueprint

Unable to access focusable elements inside a Popover2 with HOVER interactionKind

Open

#5,851 创建于 2023年1月17日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)TypeScript (20,263 star) (2,167 fork)batch import
Domain: accessibilityP2Package: popover2Type: enhancementhelp wanted

描述

Code Sandbox

"Hover" button in "Interactions" example

Steps to reproduce

Tab to open hover button

Actual behavior

Unable to access menu items with keyboard navigation

Expected behavior

Should be able to tab to menu items without popover closing, or otherwise able to access menu items with keyboard navigation

Possible solution

Is the user expected to implement custom open control if accessibility is required? It would be nice to get this out of the box!

Note that CLICK interactionKind works as expected, perhaps if TAB key opens the popover it acts more like how the click action currently works.

贡献者指南

技术栈
typescriptreact
领域
frontendaccessibility
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
React basicsUnderstanding of keyboard eventsFamiliarity with Blueprint's Popover2 component
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
Investigate the Popover2 component's source code, specifically the interaction handlers for HOVER interactionKind. The goal is to ensure that when the popover is opened via hover and the user presses Tab, focus moves to the first focusable element inside the popover without closing it. Refer to the existing CLICK interactionKind implementation for a pattern. Key files likely include the Popover2 component and its interaction management logic.