Type: New Feature
Affects Version/s: None
Fix Version/s: None
Lifted from a click.dev post by Ahmed Mohombe:
"I made a few proof of concept tests with bigger forms with Click, and unfortunately having no
browser side validation makes them very uncomfortable for the users.
I made the tests last week in our intranet, replacing(trying to ) our internal survey
application. I overlogged the forms, and supplied extra forms for the users to get from
them feedback about the usability of the forms/framework:
Even if I tried to design the forms nice, with many hints and help texts, it seems that most users
- users will fill many fields wrong: at every 4 fields one triggers a validation error.
from e-bay? ). It seems that they are accustomed to fast feedback about field validation errors,
and use them as 'help'/'guide'.
-> it was a nightmare to make the forms without direct Click support for the fieldset HTML element).
A very simple solution seems to me to automatically integrate wForms into the Form Control:
wForms from http://www.formassembly.com/
I think this will require just to follow some conventions and a few defaults so the Form
control should enforce them if the programmers selects "form.setJSValidation(true);".
It has support for i18n and it seems by far the most complete and less bug bloated form library.
lay way behind.
compliance is a very hard work, takes lot of time and test cases.
kills the simplicity of Click and it's arguments over other MVCs, so the Form Control should be by
What do you think, should we use wForms?"