type="number" input treats -. sequence as neither number nor not
Reported by
j...@communicraft.com,
Jul 20 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3157.0 Safari/537.36 Steps to reproduce the problem: 1. Enter the text -.1 into a number field with required set What is the expected behavior? Either the text is treated the same as -0.1 (Firefox behaviour) or it is treated the same as -. (that is, a full number has not been input) and so not fulfilling the required validation attribue What went wrong? The value is interpreted as being content as far as the required validation goes, but not as being content as far as the number produced goes, so validation passes while the input is still not giving a value. Did this work before? N/A Chrome version: 61.0.3157.0 Channel: n/a OS Version: 10.0 Flash Version:
,
Jul 21 2017
,
Jul 21 2017
@jonh-- Thanks for posting the issue. Could you please provide the Sample files or URL to reproduce the issue. That would help us in triaging the issue. Thanks in advance.
,
Oct 12 2017
As there is no response from the reporter for comment #3 for more than two months. Hence, closing the issue as wontFix. Please feel free to raise a new issue if the issue is reproduced with latest chrome builds. Thanks...!! |
||||
►
Sign in to add a comment |
||||
Comment 1 by j...@communicraft.com
, Jul 20 2017