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.

Sign up for GitHub

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

Jump to bottom

[Bug Report][3.6.12] VNumberInput range validation too eager #20171

Closed
kingyue737 opened this issue Jul 16, 2024 · 0 comments · Fixed by #20211
Closed

[Bug Report][3.6.12] VNumberInput range validation too eager #20171

kingyue737 opened this issue Jul 16, 2024 · 0 comments · Fixed by #20211
Labels
C: VNumberInput T: bug Functionality that does not work as intended/expected

Comments

@kingyue737
Copy link
Contributor

Environment

Vuetify Version: 3.6.12
Vue Version: 3.4.31
Browsers: Edge 126.0.0.0
OS: Windows 10

Steps to reproduce

  1. Set min as 5, max as 125
  2. Type 100

bug

Expected Behavior

100 in VNumberInput

Actual Behavior

The number in input becomes 125

Validation is too eager. It's hard to input a number actually allowed.

Reproduction Link

https://play.vuetifyjs.com/#...
@yuwu9145 yuwu9145 added T: bug Functionality that does not work as intended/expected C: VNumberInput and removed S: triage labels Jul 18, 2024
@yuwu9145 yuwu9145 mentioned this issue Jul 22, 2024
Merged
@yuwu9145 yuwu9145 mentioned this issue Aug 15, 2024
Closed
@snyk-io snyk-io bot mentioned this issue Aug 31, 2024
Open
@brittag brittag mentioned this issue Sep 3, 2024
Merged
@jonathanestefani jonathanestefani mentioned this issue Sep 24, 2024
Open
@WontonSam WontonSam mentioned this issue Oct 7, 2024
Open
@aurelienfvre aurelienfvre mentioned this issue Nov 10, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: VNumberInput T: bug Functionality that does not work as intended/expected
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(VNumberInput): prevent NaN & properly handle js number quirks vuetifyjs/vuetify
2 participants
@yuwu9145 @kingyue737