Incorrect value for valueMissing in validityState for input type=number
Categories
(Core :: DOM: Forms, defect)
Tracking
()
People
(Reporter: ibrahim.bendebka, Unassigned)
References
Details
Attachments
(1 file)
1.18 KB,
text/html
|
Details |
Steps to reproduce:
Write an HTML input[type=number] element with the require
attribute
write in it a "badInput" value like 1e
Actual results:
in js the validityState object has this values:
{"badInput":true, "customError":false, "patternMismatch":false, "rangeOverflow":false, "rangeUnderflow":false, "stepMismatch":false, "tooLong":false, "tooShort":false, "typeMismatch":false, "valid":false, "valueMissing":false}
badInput
is true
valuesMissing
is false
and the element value is an empy string.
Expected results:
valuesMissing
should be true by my understanding
Comment 1•11 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•11 days ago
|
||
Nightly:
{"badInput":true, "customError":false, "patternMismatch":false, "rangeOverflow":false, "rangeUnderflow":false, "stepMismatch":false, "tooLong":false, "tooShort":false, "typeMismatch":false, "valid":false, "valueMissing":false}
Chrome:
{"badInput":true, "customError":false, "patternMismatch":false, "rangeOverflow":false, "rangeUnderflow":false, "stepMismatch":false, "tooLong":false, "tooShort":false, "typeMismatch":false, "valid":false, "valueMissing":true}
Updated•10 days ago
|
Description
•