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
{{ message }}
This repository has been archived by the owner on Dec 24, 2021. It is now read-only.
A while back (task 880) we improved form validation by utilising the HTML Required attribute, but it was noted that it was not universally supported. At the time it was proposed that we utilise the Foundation Abide validation (http://foundation.zurb.com/sites/docs/v/5.5.3/components/abide.html) with Adam noting ...the demo of Abide in Safari seemed OK (I'm also using an older Safari 8).
I have explored Abide further and found out why it did not work in earlier testing. I have been able to get a prototype working (mods to html::multiColFormand form-default error messages) and see many benefits in utilising its rich feature set. It would be important to make sure it was an opt in solution.
In a nutshell, abide needs a validation message attached to each field to be tested. Example:
<divclass="input-wrapper"><label>Email Address <small>required</small><inputtype="email" required></label><smallclass="error">A valid email address is required.</small></div>
Aside from validating the standard input types, it also offers custom patterns (the default patterns are listed below). You use the patterns via
A while back (task 880) we improved form validation by utilising the HTML Required attribute, but it was noted that it was not universally supported. At the time it was proposed that we utilise the Foundation Abide validation (http://foundation.zurb.com/sites/docs/v/5.5.3/components/abide.html) with Adam noting ...the demo of Abide in Safari seemed OK (I'm also using an older Safari 8).
I have explored Abide further and found out why it did not work in earlier testing. I have been able to get a prototype working (mods to
html::multiColForm
andform
-default error messages) and see many benefits in utilising its rich feature set. It would be important to make sure it was an opt in solution.In a nutshell, abide needs a validation message attached to each field to be tested. Example:
Aside from validating the standard input types, it also offers custom patterns (the default patterns are listed below). You use the patterns via
The link above goes into a lot more detail about the features and customisation.
The text was updated successfully, but these errors were encountered: