> > Hehe, I ran into this one several times :-) > > The problem is not in CForms, but in HTML: each form element (input, > button, etc) is added as a property of the form it belongs to. Problem > is that these new properties hide those that may already exist with the > same name on the form. > > And a form already has a "submit" property which is a function, which > means that if you have an <input name="submit">, we can no more > programmatically submit the form using "form.submit()"... > > So the solution is to avoid naming CForms widget "submit"... Maybe we > could enforce this at the form definition parsing level? > > Sylvain
Good idea. Then users get better informed about the possible errors with submit-on-change. I'll look if I have some time to provide a patch, OK? Bart.
