On Thu, 6 Jan 2011, Mounir Lamouri wrote:
> > On Fri, 22 Oct 2010, Anne van Kesteren wrote:
> >> I think it would be better to simply omit that trailing comma. Which
> >> should be allowed. If the specification currently does not allow that
> >> (somehow) it would be a bug and is just something t
On 01/06/2011 12:40 AM, Ian Hickson wrote:
>
> This thread led me to realise there were a number of problems in the spec
> with the multiple="" attribute as applied to type=email, including a poor
> definition of how list="" applies, a poor definition of how selectedOption
> applies, an incoher
This thread led me to realise there were a number of problems in the spec
with the multiple="" attribute as applied to type=email, including a poor
definition of how list="" applies, a poor definition of how selectedOption
applies, an incoherent expectation that the selection API should apply t
On 23/10/2010 22:16, Garrett Smith wrote:
On 10/22/10, Anne van Kesteren wrote:
On Fri, 22 Oct 2010 19:44:42 +0200, Boris Zbarsky wrote:
On 10/22/10 1:25 PM, Garrett Smith wrote:
What is wrong with splitting on comma, e.g.
var validAddressList = inp.value.split(",");
That depends on wha
On Fri, Oct 22, 2010 at 5:07 PM, Jonas Sicking wrote:
> Actually, pages like gmail needs and uses the whole string "Aryeh
> Gregor ", so you don't want to strip it down
> to just the email address. I suspect that we'll end up having to
> support this format of email addresses too, either as anothe
On 10/22/10, Anne van Kesteren wrote:
> On Fri, 22 Oct 2010 19:44:42 +0200, Boris Zbarsky wrote:
>> On 10/22/10 1:25 PM, Garrett Smith wrote:
>>> What is wrong with splitting on comma, e.g.
>>>
>>> var validAddressList = inp.value.split(",");
>>
>> That depends on what meaning of "email address"
On Fri, 22 Oct 2010 23:07:47 +0200, Jonas Sicking wrote:
Actually, pages like gmail needs and uses the whole string "Aryeh
Gregor ", so you don't want to strip it down
to just the email address. I suspect that we'll end up having to
support this format of email addresses too, either as another @
On Fri, 22 Oct 2010 23:09:41 +0200, Jonas Sicking wrote:
On Fri, Oct 22, 2010 at 2:57 AM, Anne van Kesteren
wrote:
I do not really get why it being comma-separated is not just the
submission format. The UI could be quite different. E.g. on the iPhone
email client it is more like an inline
On Fri, Oct 22, 2010 at 2:57 AM, Anne van Kesteren wrote:
> On Thu, 21 Oct 2010 15:31:04 +0200, Mounir Lamouri
> wrote:
>>
>> For the moment, a valid email address list is a set of comma-separated
>> tokens where each tokens are a valid email address so in the case of
>> "f...@bar.com, ", "f...@b
On Fri, Oct 22, 2010 at 11:31 AM, Aryeh Gregor wrote:
> On Thu, Oct 21, 2010 at 9:31 AM, Mounir Lamouri
> wrote:
>> Hi,
>>
>> For the moment, a valid email address list is a set of comma-separated
>> tokens where each tokens are a valid email address so in the case of
>> "f...@bar.com, ", "f...@b
On Thu, Oct 21, 2010 at 9:31 AM, Mounir Lamouri
wrote:
> Hi,
>
> For the moment, a valid email address list is a set of comma-separated
> tokens where each tokens are a valid email address so in the case of
> "f...@bar.com, ", "f...@bar.com" is a valid email address but not "".
>
> Unfortunately,
On Fri, 22 Oct 2010 19:44:42 +0200, Boris Zbarsky wrote:
On 10/22/10 1:25 PM, Garrett Smith wrote:
What is wrong with splitting on comma, e.g.
var validAddressList = inp.value.split(",");
That depends on what meaning of "email address" is used here. Is:
"Zbarsky, Boris"
a valid "email
On 10/22/10 1:25 PM, Garrett Smith wrote:
What is wrong with splitting on comma, e.g.
var validAddressList = inp.value.split(",");
That depends on what meaning of "email address" is used here. Is:
"Zbarsky, Boris"
a valid "email address"?
-Boris
On 10/22/10, Rob Crowther wrote:
> Anne van Kesteren wrote:
>> I do not really get why it being comma-separated is not just the
>> submission format. The UI could be quite different. E.g. on the iPhone
>> email client it is more like an inline list. I think the specification
>> is simply not abstr
Anne van Kesteren wrote:
I do not really get why it being comma-separated is not just the
submission format. The UI could be quite different. E.g. on the iPhone
email client it is more like an inline list. I think the specification
is simply not abstract enough here, as it is for the other cont
On Thu, 21 Oct 2010 15:31:04 +0200, Mounir Lamouri
wrote:
For the moment, a valid email address list is a set of comma-separated
tokens where each tokens are a valid email address so in the case of
"f...@bar.com, ", "f...@bar.com" is a valid email address but not "".
I do not really get why i
On 10/21/2010 03:31 PM, Mounir Lamouri wrote:
> Hi,
>
> For the moment, a valid email address list is a set of comma-separated
> tokens where each tokens are a valid email address so in the case of
> "f...@bar.com, ", "f...@bar.com" is a valid email address but not "".
>
> Unfortunately, as soon
Hi,
For the moment, a valid email address list is a set of comma-separated
tokens where each tokens are a valid email address so in the case of
"f...@bar.com, ", "f...@bar.com" is a valid email address but not "".
Unfortunately, as soon as you want to put a UI on top of that, values
will always b
18 matches
Mail list logo
