26119 2014-06-17 16:24:56 +0000 An upper limit to the length of a year should be specified. 2016-04-27 18:15:20 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED WORKSFORME P2 normal --- 1 ssheehan dave.null bzbarsky mike mounir public-html-admin public-html-wg-issue-tracking robin travil public-html-bugzilla oldest_to_newest 107946 0 ssheehan 2014-06-17 16:24:56 +0000 The text for parsing a year in <input type="date"> says a year should be of the form: "Four or more ASCII digits, representing year, where year > 0" This should probably have a reasonable upper limit on the length of the year. I suggest this be exactly four ASCII digits. 107947 1 bzbarsky 2014-06-17 16:27:28 +0000 That doesn't seem very future-compatible... 107995 2 mounir 2014-06-18 10:26:14 +0000 Does Date (JS) has an upper limit? 108000 3 robin 2014-06-18 11:46:50 +0000 FWIW ISO 8601 supports years beyond 9999 (though somewhat shakily). Obviously, I'd expect real-world date parsers to regularly fail on those. 108006 4 bzbarsky 2014-06-18 14:05:31 +0000 > Does Date (JS) has an upper limit? Sort of. It has the limit that only dates whose numeric value is < 1e8 days (so about 273000 years from 1970) are representable. It also defines the string format as YYYY-MM-DDTHH:mm:ss.sssZ, based on ISO8601, but also defines a string format for years past that point. See http://people.mozilla.org/~jorendorff/es6-draft.html#sec-extended-years new Date(4.32e15).toISOString() seems to work in UAs, modulo https://bugzilla.mozilla.org/show_bug.cgi?id=730831 in Firefox. 108481 5 mounir 2014-06-30 10:06:12 +0000 Would that make sense to say that the year's upper-limit for <input type='date'> should match the one in JS' Date? 126215 6 travil 2016-04-27 18:15:20 +0000 HTML5.1 Bugzilla Bug Triage: Works for me I'm guessing that by the time we need to worry about extending the year's date to anything beyond 4 digits, we'll be using some other time measurement system (Galactic time?) If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!