[Bug 16651] New: "A valid non-negative integer representing a year" allows <time>0</time>, and the associated parsing algorithm step interprets it as year 0, which is inconsistent with all the other date-parsing algorithms that reject year 0

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16651

           Summary: "A valid non-negative integer representing a year"
                    allows <time>0</time>, and the associated parsing
                    algorithm step interprets it as year 0, which is
                    inconsistent with all the other date-parsing
                    algorithms that reject year 0
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#the
                    -time-element
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Specification: 
Multipage: http://www.whatwg.org/C#the-time-element
Complete: http://www.whatwg.org/c#the-time-element

Comment:
"A valid non-negative integer representing a year" allows <time>0</time>, and
the associated parsing algorithm step interprets it as year 0, which is
inconsistent with all the other date-parsing algorithms that reject year 0

Posted from: 86.185.44.58
User agent: Opera/9.80 (X11; Linux x86_64; U; en-GB) Presto/2.10.229
Version/11.60

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Monday, 9 April 2012 10:58:35 UTC