palantir/blueprint

Unable to access focusable elements inside a Popover2 with HOVER interactionKind

Open

#5,851 opened on 2023年1月17日

GitHub で見る
 (1 comment) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.