W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

(unknown charset) [whatwg] autocompletetype vs autocomplete, type attributes

From: (unknown charset) Kornel Lesiński <kornel@geekhood.net>
Date: Wed, 25 Jan 2012 20:03:51 -0000
Message-ID: <op.v8noophkte2ec8@aimac.local>

Google's annoucement of autocompletetype type[1] uses type="text" field  
for e-mail input, which doesn't seem right given that HTML has <input  
type="email"> already.

Should <input type="text" autocompletetype="email"> behave just like  
<input type="email">? Similar ambiguity exists for <input type=text  
autocompletetype=phone-full> and <input type=tel>.

Why not fold autocompletetype types into the existing type attribute (or  
autocomplete attribute)? Type could be redefined as space-separated list,  
so <input type="cc-full-name name-full section-billing"> could work just  
like autocompletetype. It would be backwards compatible with HTML5 types  
and fall back to text for new types or lists.

Having all of type, autocomplete and autocompletetype looks quite messy.


regards, Kornel Lesi?ski
Received on Wednesday, 25 January 2012 12:03:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC