W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2006

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

From: Hallvord R M Steen <hallvors@gmail.com>
Date: Thu, 6 Jul 2006 15:29:17 +0200
Message-ID: <dd4c8a40607060629w205e6644pf1ede12973830e9d@mail.gmail.com>
On 01/02/06, Hallvord Reiar Michaelsen Steen <hallvord at hallvord.com> 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 first. Many ASP.NET
sites wrap the entire page in a FORM that is submitted from JavaScript
as part of site navigation. The spec as it stands will prevent
navigation on any ASP.NET site combining maxlength and a hint text
longer than it. For example

<input maxlength="5" name="zip" value="Zip code">

prevents navigating costco.com .

Know you're working on web apps mostly these days, Ian, but I hope you
get a chance to rework this before more UAs implement it.

Proposed changes to the spec: under tooLong I suggest this:

" and the control has more than the specified number of code points"

changed to

the control's value is not its defaultValue and the control has more
than the specified number of code points

-- 
Hallvord R. M. Steen
Received on Thursday, 6 July 2006 06:29:17 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:47 UTC