palantir/blueprint

MultiSelect tagInputProps: How to avoid input focus when onRemove triggered?

Open

#3,310 opened on Jan 22, 2019

View on GitHub
 (7 comments) (0 reactions) (0 assignees)TypeScript (20,263 stars) (2,167 forks)batch import
P3Package: selectType: enhancementhelp wanted

Description

Environment

  • Package version(s): 2
  • Browser and OS versions:

Question

Is it possible to prevent input focus when onRemove triggered? Thanks in advance!

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
feature
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.
1-3 hours
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.
mostly clear
Prerequisites
Basic knowledge of ReactFamiliarity with Blueprint's MultiSelect component
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current behavior of MultiSelect's onRemove callback and see if there is a way to prevent focus from shifting back to the input. Look for existing props like `popoverProps` or `tagInputProps` that might control focus. If not, consider proposing a new prop to allow users to disable focus on remove. Check the source code at `packages/core/src/components/select/multiSelect.tsx` and related files. Review any existing discussions in the issue comments for potential solutions.