On 1/17/06, Hallvord Reiar Michaelsen Steen <[EMAIL PROTECTED]> wrote: > Kayak.com is in trouble because they've set a maxlength that is > smaller than some of the data the script sets input value to. (I'm > sending them some feedback about that). However, the site shows an > interesting problem: the UA (testing in Opera 9) does not submit the > form because of the validation problem, but the onsubmit event has > been called, meaning the site has disabled its submit button. Hence, > the user has no way to fix the data and resubmit (even if she > actually understands what the error is). > > Should we really fire onsubmit if the UA prevents submitting the > form? Button-disabling-on-submit scripting isn't exactly rare..
I think you have to fire onsubmit, there are also lots of other things people do onsubmit - copying information into hidden fields, calling tracking scripts etc. It's really an issue with the user agent. The problem here is actually a problem of backwards compatibility, current user agents do not stop submission when maxlength is too long. This means valid content, The HTML 4.01 doesn't say that having a value longer than maxlength is an error, won't work in user agents. You should implement the behaviour only for documents identified as a Web Forms 2.0 user agent. Jim.
