WHATWG Wiki - User contributions [en]

Time element

2009-07-27T00:08:28Z

KuraFire: /* Synopsis of the issue(s) */

== Bugzilla links ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]

== Synopsis of the issue(s) ==

==== 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.

Time element

2009-07-27T00:07:32Z

KuraFire: /* Synopsis of the issue(s) */

== Bugzilla links ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]

== 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.

Time element

2009-07-27T00:07:07Z

KuraFire:

== Bugzilla links ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]

== 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.

Time element

2009-07-27T00:04:43Z

KuraFire: Changed the header

== Bugzilla links ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]

== Synopsis of the issue(s) ==

* 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.

Time element

2009-07-27T00:04:15Z

KuraFire:

== Bug 7145 ==

[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]

== Synopsis of the issue(s) ==

* 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.

Time element

2009-07-27T00:03:57Z

KuraFire: New page: == Bug 7145 == http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01" == Synopsis of the issue(s) =...

== Bug 7145 ==

[[http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]]

== Synopsis of the issue(s) ==

* 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.

Main Page

2009-07-26T23:51:26Z

KuraFire: Added new page, Issue Discussion

Welcome to the WHATWG Wiki!

You can be a part of our community, making proposals for the next version of HTML5. This wiki is made available for you for drafting proposals, for writing essays, for keeping track of HTML-related issues, and so forth. Anyone can create an account and contribute content.

Before you begin, you may wish to read our [[WHATWG Wiki:Contribution Guidelines|contribution guidelines]].

==Purpose==
The purpose of the WHATWG Wiki is to create a place for WHATWG contributors to post and compile their own proposals and ideas regarding WHATWG specifications. The specifications themselves will not be available for editing via this wiki. However, ideas you post here may find their way into current and future WHATWG specifications.

== Main sections and Quick links ==
* [[FAQ]]
* [[Implementations]]
* [[What you can do]] — '''[[Reviewing HTML5|Help us review HTML5!]]
* [[Authoring|Using HTML 5 in your Web site]]
* [[Presentational elements and attributes]]
* [[HTML vs. XHTML]]
* [[HTML5 Presentations]]
* [[Issue Discussion]]
* [[Feature Proposals]]
* [[Spec coordination]]
* [[IDE]]

==WHATWG Specifications==
* [[HTML 5]]
* [[Web Workers]]

==Communicating with the community==
The WHATWG community has several channels of communication:
* [http://www.whatwg.org/mailing-list Mailing lists]
* [http://hixietracker.blogspot.com/ Hixie Tracker]; A blog that only tracks e-mails to the WHATWG list that are written by the editor
* [http://blog.whatwg.org/ The blog], including [http://blog.whatwg.org/category/weekly-review Mark Pilgrim's column "This week in HTML5"]
* [http://www.w3.org/html/planet/ W3C's "HTML5 planet"]
* [http://forums.whatwg.org/ The forum]
* [[IRC]]
* [http://lastweekinhtml5.blogspot.com/ Jean-Baptiste's "Last week in HTML5"]; A blog that highlights controversial comments on the IRC channel
* [http://wiki.whatwg.org/ This wiki]