Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
On Oct 30, 2008, at 2:19 PM, Tab Atkins Jr. wrote: I have no problem with input type=email. type=address would be very confusing (see what people think about the address element today!), and worse, can legitimately be thought to be for inputting physical addresses. No one will ever think that type=email is for composing an email - it's a single piece of information (composing an email requires several) and it's in the input family which is for small pieces of information (an entire email is much larger than the natural size of an input). In the multiple case, I'm fine with either [type=emails] or [type=email][multiple=multiple]. aolMe too./aol Are there any other situations where adding a multiple attribute could work similarly, other than select? -- Andy Lyttle [EMAIL PROTECTED]
Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
Indeed, INPUT[type=email] is confusing as well. I would add [type=address] and [type=address-list] as candidates because an e-mail address is the most common type of an address on the Web (the e-mail part can be omitted IMHO). Using INPUT[multiple=multiple] seems like a good idea as well. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eduard Pascual Sent: Thursday, October 30, 2008 3:28 AM To: Matthew Paul Thomas Cc: WHAT working group Subject: Re: [whatwg] Web forms 2,input type suggestions (Michael A. Puls II) What about multi-email, email-list or email-addresses? The last one is the one I most like, and the most explicit, with the only (minor) drawback that it's the longest. Anyway, that's just a suggestion. BTW, the same argument could be made on type=email, since someone could easily think it expects an entire message.
Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
On Thu, Oct 30, 2008 at 1:47 PM, Kristof Zelechovski [EMAIL PROTECTED]wrote: Indeed, INPUT[type=email] is confusing as well. I would add [type=address] and [type=address-list] as candidates because an e-mail address is the most common type of an address on the Web (the e-mail part can be omitted IMHO). Using INPUT[multiple=multiple] seems like a good idea as well. Chris I have no problem with input type=email. type=address would be very confusing (see what people think about the address element today!), and worse, can legitimately be thought to be for inputting physical addresses. No one will ever think that type=email is for composing an email - it's a single piece of information (composing an email requires several) and it's in the input family which is for small pieces of information (an entire email is much larger than the natural size of an input). In the multiple case, I'm fine with either [type=emails] or [type=email][multiple=multiple]. ~TJ
Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
On Sun, 15 Jul 2007, Alex Vincent wrote: I've held off on commenting about the new types suggested for input so far, but I should mention this: Web Forms 2 as it currently stands has twenty-four different types of input elements. Ten from HTML 4, fourteen new ones in this spec. Please, please, don't overload it any more than is absolutely necessary. We're down to 20 total, 10 from HTML4 and 10 new ones, 6 of which are date-related, 2 of which are numeric, and 2 of which are text-based. We'll probably add type=color soon, and maybe type=emails or some such some time after that. In general though I agree that we should keep things to a minimum, just as with all parts of the Web platform. Cheers, -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
On Oct 29, 2008, at 6:40 PM, Kristof Zelechovski wrote: Declare INPUT[type=mailing-list] instead of INPUT[type=emails], please. Type=emails is ugly and confusing (as it seems to expect messages). ... emails is indeed ugly, but mailing-list would be even worse. A mailing list usually has a single address. -- Matthew Paul Thomas http://mpt.net.nz/ ---AV Spam Filtering by M+Guardian - Risk Free Email (TM)---
Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
On Thu, Oct 30, 2008 at 1:16 AM, Matthew Paul Thomas [EMAIL PROTECTED] wrote: On Oct 29, 2008, at 6:40 PM, Kristof Zelechovski wrote: Declare INPUT[type=mailing-list] instead of INPUT[type=emails], please. Type=emails is ugly and confusing (as it seems to expect messages). ... emails is indeed ugly, but mailing-list would be even worse. A mailing list usually has a single address. What about multi-email, email-list or email-addresses? The last one is the one I most like, and the most explicit, with the only (minor) drawback that it's the longest. Anyway, that's just a suggestion. BTW, the same argument could be made on type=email, since someone could easily think it expects an entire message.
Re: [whatwg] Web forms 2, input type suggestions (Michael A. Puls II)
On 10/30/08, Eduard Pascual [EMAIL PROTECTED] wrote: On Thu, Oct 30, 2008 at 1:16 AM, Matthew Paul Thomas [EMAIL PROTECTED] wrote: On Oct 29, 2008, at 6:40 PM, Kristof Zelechovski wrote: Declare INPUT[type=mailing-list] instead of INPUT[type=emails], please. Type=emails is ugly and confusing (as it seems to expect messages). ... emails is indeed ugly, but mailing-list would be even worse. A mailing list usually has a single address. What about multi-email, email-list or email-addresses? The last one is the one I most like, and the most explicit, with the only (minor) drawback that it's the longest. Anyway, that's just a suggestion. BTW, the same argument could be made on type=email, since someone could easily think it expects an entire message. INPUT[type=email][multiple=1] c.f. SELECT[multiple=1]
