[Bug 14908] New: 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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14908

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#dat
                    es-and-times
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, kennyluck@csail.mit.edu


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

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 23 November 2011 08:11:36 UTC