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
My issue are the numeric inputs (all packages except ant):
In Safari (and according to the HTML Standards) is target.value of the onChange-Event undefined, if the validation (HTML-standard) of the string fails.
This leads to the fact, that you can enter all letters (e.g. '8$%&') into the input field, but you won't get an error of the validator, as uniforms converts it in 'undefined'.
I've built a custom field based on cleave.js for my project which resolves the issue -- I think cleave.js could be useful for some other fields in uniforms.
Best wishes
Adrian Schneider
The text was updated successfully, but these errors were encountered:
Hi @adrianschneider94. I'm aware of that. That is because each NumField (except the one in uniforms-antd) have an internal class to fix numeric inputs handling in React < 16. There's even a comment to make it optional and I think that it's getting more and more important.
Just for the record - we won't use any external package for that, simply delegate it to React (but still try to do our best in older versions).
Hi there, great package!
My issue are the numeric inputs (all packages except ant):
In Safari (and according to the HTML Standards) is target.value of the onChange-Event undefined, if the validation (HTML-standard) of the string fails.
This leads to the fact, that you can enter all letters (e.g. '8$%&') into the input field, but you won't get an error of the validator, as uniforms converts it in 'undefined'.
I've built a custom field based on cleave.js for my project which resolves the issue -- I think cleave.js could be useful for some other fields in uniforms.
Best wishes
Adrian Schneider
The text was updated successfully, but these errors were encountered: