4107541076How can I validate that a Formview field has a non-empty value?
similar scenario was discussed in dialog/ux, i think in version 11 forum.
You can check out a demo below: See the Pen Instant Form Validation by Site Point (@Site Point) on Code Pen.
Once that scripting is implemented, we’re actually only a couple of skips and hops away from a complete polyfill.
If you’ve followed along, you know about controlled inputs and simple things they enable, like disabling the Submit button when some fields are missing or invalid. While a disabled button is nice, the reason for that is not immediately apparent to the users. This is an important question to ask yourself, as different requirements might warrant different error representations. The way you want to display errors influences how you might represent them.
Now, to mark the bad inputs, we need to ask ourselves a couple of questions. Well, it’s all about the experience you want to provide. For the purpose of this post, I’m going to do with the simplest one — marking red the bad inputs, without anything else.
We could just choose to ignore those browsers, but I think that would be a shame, especially when the problem is so simple to workaround.
It just means a bit more convoluted code – we have to get the collections of So there we have it – a simple and non-intrusive enhancement for instant form validation, providing accessible and visual cues to help users complete forms.
It will accept the current values of the fields and returns us the JS Bin on If you look at the JS Bin above, you may notice something odd.
On subsequent focuses, though, the error would be shown. A nice final touch might be to force display of errors on all fields, regardless of whether they have been in focus, when the user hovers or clicks a disabled submit button.
For legacy browsers that don’t implement these attributes, we can use their values as the basis of a polyfill.
Such a script is beyond the scope of this article, but if you wanted to develop it further, all of the basic blocks are there – testing whether a field should be validated, validating a field against a pattern and/or required, and binding trigger events.
I have to confess, I’m not sure it’s really worth it!