react-component / react-component/pagination
<input> in simple mode does not handle onBlur event when goButton is not showed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 674
- Forks
- 333
- Avg merge
- 12m
- Merged PRs (30d)
- 1
Description
<input> in simple mode should handle onBlur event when goButton is not showed so that this.prop.onChange() is called and the content for the currentInputValue page can be put on display. Otherwise, user may be confused as the number showing in the input is not related to the content showing.
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
Inspect src/Pagination.jsx at lines 446-453, starting with the simple-mode input and its current onBlur behavior when goButton is absent. Done means the input blur calls this.prop.onChange() and the displayed content matches the currentInputValue page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100