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).
Time element: Difference between revisions
Jump to navigation
Jump to search
m (Changed the header) |
mNo edit summary |
||
| Line 5: | Line 5: | ||
== Synopsis of the issue(s) == | == Synopsis of the issue(s) == | ||
[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145] | |||
* The <code><time></code> element should accept date and/or time inputs of varying precision, such as YYYY or YYYY-MD. 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 <code><time></code> element only allows for <code>datetime</code> values as imprecise as a specific day, e.g. YYYY-MM-DD. | * The <code><time></code> element should accept date and/or time inputs of varying precision, such as YYYY or YYYY-MD. 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 <code><time></code> element only allows for <code>datetime</code> values as imprecise as a specific day, e.g. YYYY-MM-DD. | ||
Revision as of 00:07, 27 July 2009
Bugzilla links
Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"
Synopsis of the issue(s)
- The
<time>element should accept date and/or time inputs of varying precision, such as YYYY or YYYY-MD. 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 fordatetimevalues as imprecise as a specific day, e.g. YYYY-MM-DD.