Bug: 0 is valid when min is a number greater than 0.
See original GitHub issue- Bug report.
For the input with type number, if the min is greater than 0, 0 still is a valid input. Note: only parsley believed its valid when javascript validation api can ascertain that number is invalid.
<input id="number" type="number" class="form-control" min="3" max="5600" step="0.01" required="" data-parsley-type="number">
https://codepen.io/anon/pen/oOpoXp?editors=101&editable=true
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
Is there a bug with min="0" in jquery validation? Or am I ...
Consider this jsFiddle. It appropriately objects to a value of -5 in the first input element and in the third, but accepts a...
Read more >Robotic Motion Planning: Bug Algorithms
By assumption, it is finite length, and intersects obstacles a finite number of times. – BUG1 does not find it. • Either it...
Read more ><input type="number"> - HTML: HyperText Markup Language
If a value is specified for min that isn't a valid number, the input has no minimum value. This value must be less...
Read more >Reverse digits of an integer with overflow handled
If the reversed integer overflows, print -1 as the output. Let us see a simple approach to reverse digits of an integer.
Read more >Why the number input is the worst input - Stack Overflow Blog
Valid numbers include more than just digits (i.e,. scientific ... Using <input type="text" inputmode="numeric" pattern="[0-9]*"> is a nice ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, that’s pretty bad. Thanks for the report. I think this was broken by #1151. I probably should not have accepted it…
Fixed and released.
Thanks again for the bug report.