17926 2012-07-18 07:18:18 +0000 "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 2012-10-05 22:50:28 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-time-element P3 normal Unsorted 1 contributor ian cmhjones ian mike contributor oldest_to_newest 70313 0 contributor 2012-07-18 07:18:18 +0000 This was was cloned from bug 16651 as part of operation convergence. Originally filed: 2012-04-06 16:22:00 +0000 ================================================================================ #0 contributor@whatwg.org 2012-04-06 16:22:32 +0000 -------------------------------------------------------------------------------- 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 ================================================================================ 75428 1 contributor 2012-10-05 22:50:28 +0000 Checked in as WHATWG revision r7435. Check-in comment: Make the year-only format for <time> more in line with how it works elsewhere. http://html5.org/tools/web-apps-tracker?from=7434&to=7435