palantir/blueprint

Tab navigation not working with Suggest

Open

#3,945 建立於 2020年1月28日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)TypeScript (20,263 star) (2,167 fork)batch import
Browser: IE (deprecated)Package: selectType: bughelp wanted

描述

Environment

  • Package version(s): 3.9.0
  • Browser and OS versions: IE11 (11.950.17134.0) / Edge (42.17134.1.0 & EdgeHTML 17.17134)

Steps to reproduce

  1. Go to https://blueprintjs.com/docs/#select/suggest
  2. Use tab key to focus on Suggest input
  3. Press tab again, and the focus will be on the blueprint logo instead of the nearest element (on Chrome, the focus will be on the "Close on select" toggle

Actual behavior

Once focused on the Suggest input, when pressing tab, the focus will be on the blueprint logo.

(In my case, something similar happens where the top element will be focused on rather than the next input.)

Expected behavior

Upon pressing tab, the focus will be on the nearest element (the "Close on select" toggle in this particular example).

(In my case, the next focus would be on the nearest input).

貢獻者指南

技術棧
typescriptreact
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of ReactUnderstanding of focus management
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Investigate the Suggest component's focus behavior in the Blueprint codebase, specifically in packages/select/src/components/suggest/. Look for how tab key navigation is handled, possibly in the onKeyDown or onFocus callbacks. Check if there is any manual focus management or tabIndex misconfiguration. Also review any linked PRs or comments for existing solutions. The expected behavior is to focus on the next interactive element after the Suggest input, such as the 'Close on select' toggle.