[whatwg] Web Forms attributes: minlength / autocomplete

Kristof Zelechovski giecrilj at stegny.2a.pl
Thu Jun 7 02:53:47 PDT 2007


These negative values are a misleading hack in that the input value it
should be trimmed in the DOM as well to be consistent.  If you need
autotrim, introduce an explicit attribute to this end.  This would make the
side effect more explicit.

Chris

 

  _____  

From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Sander
Sent: Wednesday, June 06, 2007 12:56 PM
To: whatwg at whatwg.org
Subject: [whatwg] Web Forms attributes: minlength / autocomplete

 

Hello,

I have a request and a question about Web Form attributes:

--- minlength ---
I'd like to see a minlength attribute that can be used on the same elements
as the maxlength attribute. The default value can be "0" unless the required
atribute is set (in that case it should be >1). The value of the element
should be trimmed of spaces at the beginning or the end before
validating/submitting (perhaps this could be made optional in which case
negative values could be used for the minlength attribute to indicate
whether the trimming has to take place or not).


--- autocomplete ---
The autocomplete attribute acts as a boolean, but its values are not
consistent to other booleans, being either attributes or variables.
Why not use autocomplete="autocomplete" or its minimised form? Is it because
it's not the "on" state that is important, but the "off" state. If so, I'd
suggest to use "true" or "false" instead or rename the attribute to
noautocomplete. If it's a backward compatibilty issue then I suggest both
on/off and true/false should be allowed.


cheers,
Sander




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20070607/ab0e00d7/attachment-0001.htm>


More information about the whatwg mailing list