react-component / react-component/input-number
Wrong order of Focus and Blur events
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 323
- Forks
- 188
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 1
Description
Reproduction link
Steps to reproduce
- Click on the first of the two
InputNumberelement in order to focus it. - Click on one of the up/down arrows (that appear when you hover) the second
InputNumberelement.
What is expected?
It should log the focus on the first element, then log the blur on the first element and lastly log the focus on the second element.
What is actually happening?
It logs the focus on the first element, then logs the focus on the second element and lastly the blur on the first element.
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
Start with the linked CodeSandbox reproduction and trace the focus and blur behavior of the two InputNumber elements. Confirm the event sequence when an arrow on the second element is clicked; done means focus on the first, blur on the first, and focus on the second are logged in that order.
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
- Clearly specified
- Newbie friendliness
- 45/100