hendry at iki.fi
Tue Jul 19 16:59:11 PDT 2005
On Tue, Jul 19, 2005 at 01:25:51 +0000, Ian Hickson wrote:
> > http://www.whatwg.org/demos/date-01/
> > Which implements input type="datetime"
> > Doesn't conform to ISO 8601 of the datetime attribute in WF2.
> It doesn't need to. That's the fallback value.
Don't quite understand this. How can it fall back onto ISO8601?
> > In the input element is there a need for datetime, datetime-local, date,
> > month, week and time, when a single ISO8601 string could perhaps do?
> How could a single one do?
I was thinking that a ISO8601 string could store all these different
datetime values. Months, week numbers etc. I wasn't thinking of them as
different widget types.
I was a bit confused about this value="DD/MM/YYYY HH:MM". This must
dictate how the form processor expects input.
Though, couldn't the UA present a date picker based on this value
> > ISO8601 support seems non-trivial. Though this could be a starting
> > point: http://delete.me.uk/2005/03/iso8601.html
> ISO8601 support is not required; one is only required to support what the
> WF2 spec says.
I thought that the UA would have to feed the ISO8601 time to the form
More information about the whatwg