Number input field min and max attributes ignored when typing
Reported by
jack.wil...@atomicmedia.co.uk,
Nov 18 2016
|
|||||
Issue description
Chrome Version : 55.0.2883.52URLs (if applicable) :
Other browsers tested:
Safari: FAIL
Firefox: FAIL
IE: FAIL
What steps will reproduce the problem?
(1) Add a NUMBER input field to a HTML page, set a 'min' and 'max' attribute on it
(2) Attempt to type a number larger than the max or lower than the min number
What is the expected result?
It will prevent entry of a number larger than the max value or lower than the min value.
What happens instead?
It permits entry of any number.
Please provide any additional information below. Attach a screenshot if
possible.
Discussion will need to be had on how to handle telling the user they've entered an invalid number because if the max is 60 and they begin typing '6', that is allowed, but as soon as they type '0' in there, it becomes invalid; so a graceful way, maybe removing the last number entered, is the best way to handle this.
,
Nov 21 2016
Unable to reproduce this issue, we tested this issue on windows 10 machine with chrome version beta 55.0.2883.52. Observed that input field is validating the minimum and maximum attributes Test Url : "http://jsfiddle.net/webvitaly/AG2wf/1/" Attached screen-cast for your reference , please look into it and let us know your observations.
,
Nov 21 2016
That's not the issue. If you take out any JavaScript and have just a plain HTML file with a number input field with a min and max attribute set, Google Chrome allows the user to type a number larger than the min and max values. It doesn't allow the user to do it with the arrows at the side of the input - which is correct.
,
Nov 22 2016
jack.wilkinson@ Thanks for your response, In this case will you mind providing a sample test case or html file to test this issue from chrome-TE team. Thanks!
,
Nov 29 2016
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 27 2016
Since the reporter has not responded from last 30 days, assuming this issue is fixed, changing the status to wontFix. Please file a new bug, if the issue is reproduced. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Nov 18 2016