react-component / react-component/cascader
keyboard shotcut issue
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 233
- Forks
- 149
- Avg merge
- 10h 23m
- Merged PRs (30d)
- 2
Description
Precondition: cursor focused in the search input,
Operation: key board <
Expect: move the cursor left.
Actual: dropdown closed
So can Cascader allow user forbidden keyboard shotcut or optimize keyboard shotcut？
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the cursor focused in the Cascader search input, then trace the keyboard handling for the < key. Done means the key moves the cursor left without closing the dropdown, with the behavior covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100