Issue Task Resolved

#105524FormEngine: input fields of type number are not working as expected when browser-native validation gets "bad input"

Ayke Halder 10/30/24, 18:07 updated 11/11/26, 13:30

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 to 1234px.
  • In Chrome insert invalid values, consisting of only 0-9 and at max one of each character +-.e:
    E.g. 1-3, then unfocus the field and then change it to 1-4.

——

Also see: https://developer.mozilla.org/en-US/docs/Web/API/ValidityState/badInput

Reviews 3

History 514

  1. Georg Ringer commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-11T13:30:14+00:00" > 11/11/26, 13:30 </span>

    Applied in changeset commit:371537332ce4f2266abbb23ca3fd6c3f40ba50fd.