You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new Chrome is more aggressive on type="date" input fields.
When using formtools the date validation works by the formtools' rules but the browser presents a calendar widget to the user that thus selects a wrong formatted date.
This is not easy to deal with. We must choose if we want to use the browser native field enhancement or block it and use ours.
A simple workaround is using a normal text type but the formtools date validation doesn't kick in and we must validate it manually (via data-ft-regex).
The text was updated successfully, but these errors were encountered:
The new Chrome is more aggressive on
type="date"
input fields.When using formtools the date validation works by the formtools' rules but the browser presents a calendar widget to the user that thus selects a wrong formatted date.
This is not easy to deal with. We must choose if we want to use the browser native field enhancement or block it and use ours.
A simple workaround is using a normal text type but the formtools date validation doesn't kick in and we must validate it manually (via
data-ft-regex
).The text was updated successfully, but these errors were encountered: