by Stuart Lamour.
Howard - any front end dev worth their salt will be fine with that and probably have included their own choice of css styles for forms, js fall-backs for older browsers and html5 forms etc, etc...
A cms can of course choose to provide a default/recommended set of js/css, but its seriously not the job of a php forms lib.
I think this makes for a clean architecture, achievable aims and a sensible baseline/spec (scopecreep : that can be expanded on...)
Anyone else have any thoughts on defining what exactly we need/want in a moodle forms lib?