Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot enter Values into Spinner #314

Closed
tsinghammer opened this issue Feb 14, 2018 · 1 comment
Closed

Cannot enter Values into Spinner #314

tsinghammer opened this issue Feb 14, 2018 · 1 comment
Assignees
Labels
Type: Bug Issue contains a defect related to a specific component.
Milestone

Comments

@tsinghammer
Copy link

tsinghammer commented Feb 14, 2018

I'm submitting a ... (check one with "x")

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=57

Plunkr Case (Bug Reports)
Please fork the plunkr below and create a case demonstrating your bug report. Issues without a plunkr have much less possibility to be reviewed.

https://plnkr.co/edit/auWr3dcu9mpqRRXidZgx?p=preview

Current behavior
If the min value of the spinner control is set to a value greater than 9 it is hard or even impossible to enter a value between min and max without using the arrows.

Expected behavior
I would like to enter the value manually without using the arrows.

Minimal reproduction of the problem with instructions
In this example we're using min=18 and max=25.
Whenever I try to enter 19 for example it would immediately set the value to 18 after entering 1 and then set it to 25 if I type on as 189 exeeds the maximum.

@tsinghammer
Copy link
Author

I don't know what would be the best solution for this issue.
Either the parseValue could be done on blur, or there could be a delay that allows to enter a whole number with a few milliseconds between each key.

@Merve7 Merve7 self-assigned this Feb 27, 2018
@Merve7 Merve7 added the Type: Bug Issue contains a defect related to a specific component. label Feb 27, 2018
@Merve7 Merve7 added this to the 1.4.2 milestone Feb 27, 2018
@Merve7 Merve7 closed this as completed in a7df47e Feb 27, 2018
@Merve7 Merve7 reopened this Feb 27, 2018
@Merve7 Merve7 closed this as completed in 72fef87 Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a defect related to a specific component.
Projects
None yet
Development

No branches or pull requests

2 participants