14908 2011-11-23 08:11:33 +0000 It's not clear to me if the "if the time-zone offset is not zero" clause here affects authoring conformance or not. FWIW, validator.nu treats <input type=datetime value=0001-01-01T00:00:00-00:00> as valid. Also, the term "best representation of the global 2012-07-18 18:39:42 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#valid-time-zone-offset-string P3 normal Unsorted 1 contributor ian ian kennyluck mike contributor oldest_to_newest 60366 0 contributor 2011-11-23 08:11:33 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html Multipage: http://www.whatwg.org/C#dates-and-times Complete: http://www.whatwg.org/c#dates-and-times Comment: It's not clear to me if the "if the time-zone offset is not zero" clause here affects authoring conformance or not. FWIW, validator.nu treats <input type=datetime value=0001-01-01T00:00:00-00:00> as valid. Also, the term "best representation of the global date and time string" doesn't seem to be used anywhere in the spec. Posted from: 114.43.120.123 by kennyluck@csail.mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0) Gecko/20100101 Firefox/8.0 60368 1 kennyluck 2011-11-23 08:18:02 +0000 Please use the pointer http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#valid-time-zone-offset-string for the first part of the comment instead. Sorry about walking away for the second part of the comment. 60369 2 mike 2011-11-23 08:47:45 +0000 (In reply to comment #0) > FWIW, validator.nu treats <input > type=datetime value=0001-01-01T00:00:00-00:00> as valid. That may not indicate anything other than validator.nu not being completely conformant to the spec with regard to this, or at least not being up to date with current spec. I'm not saying either way -- just that the behavior would need to be checked against the spec. 60370 3 mike 2011-11-23 08:54:01 +0000 OK, after looking at the spec, the definition of "valid time-zone offset string" at http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#valid-time-zone-offset-string is definitely stating document-conformance requirements. So if validator.nu is not checking those requirements correctly, we need to fix it. 61187 4 ian 2011-12-07 23:49:06 +0000 I'm confused about what this bug is requesting or asking. Can someone clarify for me what the question or bug is here? 61340 5 ian 2011-12-09 22:22:07 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 4