[whatwg] Suggested changes to Web Forms 2.0, 2004-07-01 working draft

[Hallvord Reiar Michaelsen Steen]

On 5 Jul 2004 at 19:22, Matthew Thomas wrote:

> > By default, all of these new types, just like the types from HTML4, 
> > must have no value selected, unless a default value is provided using 
> > the value attribute.
> 
> 36. Suggestion: *Please* remove this requirement, at least
>      for the date-/time-related controls. I have never seen,
>      in any graphical toolkit, a timepicker or datepicker
>      control (or even a calendar control) that did not have a
>      default value.

Agree. Perhaps add something like..

    The "value" attribute may be used with date and time types to suggest 
    an initial date/time for any calendar widget the UA may show. If 
    omitted current date and time is used.

(That might also give a nice way for the server to indicate what time 
zone it is in? I'm not sure about this suggestion because the only 
times I struggle with time zone calculation is when I fly somewhere.. 
Perhaps something like the following would be useful?)

    The UA may parse any value attribute for a time zone indication and 
    may use that time zone when presenting the calendar/date picker UI to 
    the user.

I also agree with the suggestion to rename local-datetime to datetime-
local. Thanks to Matthew to give a very sensible reason for it :-)
-- 
Hallvord Reiar Michaelsen Steen
hallvors at online.no / www.hallvord.com