Re: [whatwg] form validation of values that aren't entered by the user

On Thu, 6 Jul 2006, Hallvord R M Steen wrote: > > On 01/02/06, Hallvord Reiar Michaelsen Steen <[EMAIL PROTECTED]> wrote: > > I've already brought up this issue because of the kayak.com search > > fields with a maxlength smaller than the length of the strings > > scripts would insert into the input

Re: [whatwg] form validation of values that aren't entered by the user

On Wed, 1 Feb 2006, Hallvord Reiar Michaelsen Steen wrote: > > I suggest that > 1) willValidate should exclude readonly controls. Nothing the user > can do about those anyway. Ok. Changed. > 2) We should ignore maxlength errors for default values. Something > like the following pseudokode: >

Re: [whatwg] form validation of values that aren't entered by the user

On 01/02/06, Hallvord Reiar Michaelsen Steen <[EMAIL PROTECTED]> wrote: I've already brought up this issue because of the kayak.com search fields with a maxlength smaller than the length of the strings scripts would insert into the input elements. This problem is more serious than we thought at

[whatwg] form validation of values that aren't entered by the user

I've already brought up this issue because of the kayak.com search fields with a maxlength smaller than the length of the strings scripts would insert into the input elements. I'd like to discuss things more generally: it is a serious UI and usability problem to validate values that are not ent