This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16651 - "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
Summary: "A valid non-negative integer representing a year" allows <time>0</time>, and...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: CR
Depends on:
Blocks:
 
Reported: 2012-04-06 16:22 UTC by contributor
Modified: 2013-04-23 23:42 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2012-04-06 16:22:32 UTC 
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
Comment 1 contributor 2012-07-18 07:18:20 UTC 
This bug was cloned to create bug 17926 as part of operation convergence.
Comment 2 Robin Berjon 2013-04-23 23:42:23 UTC 
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: Accepted
Change Description: none
Rationale: Has already been fixed.