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

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

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 15 Aug 2006 10:17:34 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0608151016210.5340@dhalsim.dreamhost.com>
On Thu, 6 Jul 2006, Hallvord R M Steen wrote:
>
> 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

Fixed this in response to the first e-mail you sent on the issue. :-)

Sorry it took so long. Wasn't sure where WF2 was going. But now that 
Mozilla is implementing it too and W3C is looking at it, the direction is 
clearer, so I'm getting around to fixing the spec again.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 15 August 2006 03:17:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:28 UTC