Bugzilla – Bug 347
replace refs to form.data.datetime with common.data.datetime + consider renaming w:datetime-tz to w:datetime
Last modified: 2008-12-20 18:49:50 CET
<MikeSmith> hsivonen: seems like there's no longer any need for separate common.data.datetime and form.data.datetime -- since HTML draft specifies "valid date and time string" for all instances where schema has w:datetime-tz or w:datetime datatype
<MikeSmith> so values of attributes for <input type=datetime> can just be changed to common.data.datetime
<MikeSmith> and w:datetime-tz can probably just be renamed to w:datetime
<MikeSmith> as far as I can see
<MikeSmith> with w:datetime being defined as a full date-time, with a required time-offset
<MikeSmith> and keeping w:datetime-local for date and time without the time-offset
see attached patch
Created attachment 6 [details]
patch with proposed changes
I have trouble believing that Hixie meant to make non-"Z" time zone designators conforming for input type=datetime. Checking.
(In reply to comment #2)
> I have trouble believing that Hixie meant to make non-"Z" time zone designators
> conforming for input type=datetime. Checking.
Did you get any resolution from Hixie about this yet? I saw your comment:
"<hsivonen> as far as I can tell, the fourth para under http://www.whatwg.org/specs/web-apps/current-work/#date-and-time-state says that any time zone is valid, but the third para requires UAs to produce only UTC results"
and I saw Hixie's response:
"<Hixie> hsivonen: yeah i wanted to allow authors to use their own time zone when setting the value"
I note that a relevant part of the 3rd paragraph you cite says:
"User agents must not allow the user to set the value to a string that is not a valid global date and time string expressed in UTC, though user agents may allow the user to set and view the time in another timezone and silently translate the time to and from the UTC timezone in the value."
Strictly in terms of document conformance (conformance of a serialized HTML document), my read of that part is: A value that's a non-Z time-zone designator is in fact valid as far as document conformance; that is, a serialized HTML document that has a value with a non-Z time-zone designator is conformant/valid (but if a conformant UA encounters such a value, it must silently translate it to the UTC timezone in the DOM).
Does that sound right, or am I missing something?
Checked in. Thanks. Filed bug 364 about renaming.