Task #105524
open
FormEngine: input fields of type number are not working as expected when browser-native validation gets "bad input"
0%
Description
Issue for input-field with "bad input"¶
If the user has provided input that the browser is unable to convert, then programmatically reading the value-property returns an empty string, even though the browser is showing the user's input to the user.
Thereby the change-event does not trigger on the second attempt of bad input, as the value-property keeps returning just the empty string again.
Reproducible with input-field of type="number":¶
- In Firefox insert any invalid value:
E.g.123px, then unfocus the field and then change it to1234px.
- In Chrome insert invalid values, consisting of only
0-9and at max one of each character+-.e:
E.g.1-3, then unfocus the field and then change it to1-4.
Also see: https://developer.mozilla.org/en-US/docs/Web/API/ValidityState/badInput
Updated by Ayke Halder about 19 hours ago
- Related to Bug #105368: Form input fields that have native browser validation do not get marked as invalid but still block any saving of a record added
Updated by Ayke Halder about 16 hours ago
- Related to Task #105526: Introduce test-option for FormEngineValidation added
Updated by Gerrit Code Review about 14 hours ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86842
Updated by Gerrit Code Review about 14 hours ago
Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/86842