A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).

Difference between revisions of "Time element"

From WHATWG Wiki
Jump to navigation Jump to search
(restructured page by different issues/enhancements rather than sections around a clustering of issues from one bug report)
m (moved Time Element to Time element: lowercase generic noun element)
(No difference)

Revision as of 01:22, 25 March 2010

Research, data, use cases, issues, and enhancements related to the HTML5 time element.

year only

The time element should accept just a year.

ISO8601 syntax
use case research

Opinions / discusion:

year month only

The time element should accept just a year and a month.

ISO8601 syntax

Opinions / discusion:

  • +1 Faruk (per Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01") One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <time> element only allows for datetime values as precise as a specific day, e.g. YYYY-MM-DD.
  • -1 Hixie - "Without clear use cases, I don't intend to change the spec here." (ibid)

month day only

The time element should accept just a month and a day.

ISO8601 syntax
use case research