palantir/blueprint

Tab navigation not working with Suggest

Open

#3,945 opened on 2020年1月28日

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