W3C home > Mailing lists > Public > public-xformsusers@w3.org > September 2017

Re: Email type

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 13 Sep 2017 12:08:03 +0200
To: "Erik Bruchez" <ebruchez@orbeon.com>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Message-ID: <op.y6h03p1qsmjzpq@steven-xps>
(On Tue, 12 Sep 2017 18:24:46 +0200, Erik Bruchez <ebruchez@orbeon.com>  
wrote:

> What would the rationale be for allowing leading and trailing spaces?

Two-fold:

1) When I type in the To: field of my mailer (using _ to make spaces  
visible)

    To: _robin@example.com_

the mail gets sent without problems. There is no ambiguity.

2) When I copy and paste addresses into a web form, I often get told that  
the email is invalid, and I end up to staring at it for some seconds  
before I realise that there's a space at the end.

As Michael points out, we have the whitespace MIP if you want to get rid  
of any spurious spaces, but I'm not sure we should require the user to  
have to do the work.

On the other hand, we don't use the same document trick as XML to allow  
spaces before and after numbers, so my complaint about copying and pasting  
is true for numbers as well...

Steven



>
> AFAICT, in XML Schema part 2 numbers, for example, do not allow leading  
> and trailing space in their lexical value.
>
> I for one much prefer values properly trimmed in the data, and we now  
> have the `whitespace` MIP which takes care of the trimming anyway. [1]
>
> -Erik
>
> [1]  
> https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_whitespace_Property
>
> On Tue, Sep 12, 2017 at 3:08 AM, Steven Pemberton  
> <steven.pemberton@cwi.nl> wrote:
>> While dealing with the telephone number type, I noticed that our email  
>> type doesn't permit leading and trailing spaces.
>>
>> I think it should. Agree?
>>
>> Steven
Received on Wednesday, 13 September 2017 10:08:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:48 UTC