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

[whatwg] [Web Forms 2.0] Last minute suggestion - The <format> element.

From: Olav Junker Kjr <olav@olav.dk>
Date: Sun, 23 Jan 2005 19:48:41 +0100
Message-ID: <41F3F189.7020603@olav.dk>
Matthew Raymond wrote:
>    Well, how about giving an attribute, such as |value|, that will be 
> processed according to a specific set of rules. At the same time, only 
> the child contents of the <format> element will be the only content that 
> the user agent should render. If the |value| attribute is not defined, 
> ISO8601 is used. 

I like it.
Since the format is not just metadata but essential for parsing the 
value (and presumably also for parsing min and max values), I think it 
should be an attribute on the input element rather than the format 
element. (I still think its a good idea with a separate format element 
with a human readable format hint.)

>    If you're referring to controls being of such a nature that they 
> _can't_ display the date in a specific format, then we can simply make 
> the <format> element "where applicable".

That's what I was referring to. "where applicable" sounds OK.

>    I presume, though, that you're talking about the possibility of 
> webmasters intentionally using applyon="entry" as a means of forcing a 
> specific format on WF2 browsers. In that case it becomes an issue of 
> consistency of interface across WF2 and legacy user agents versus 
> presentational abuse.

Date entry should be either unambiguous (e.g. picking from a calendar) 
or consistently in the same format across sites. Otherwise users will 
buy plane tickets for the wrong dates and will be unhappy.

Olav Junker Kj?r
Received on Sunday, 23 January 2005 10:48:41 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:20 UTC