palantir/blueprint

Tab navigation not working with Suggest

Open

#3,945 opened on Jan 28, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
Browser: IE (deprecated)Package: selectType: bughelp wanted

Description

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).

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of ReactUnderstanding of focus management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
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.