The problem was not with input type text, as described above, but with input type checkbox (as seen in the example). checkboxes are different from other input types, since only checked items are transmitted. The problem existed, when they were specified literally in the HTML form. I think, i fixed these cases now in oacs-head and oacs-5-3.
concerning customization: i am not sure, what you have exactly in mind. there are multiple ways to customize form fields. if you want certain behavior on multiple form fields, the most flexible way is to subclass existing form field types. Look through the provided types in form-field procs. The verison in head has as well conditional properties.
