HTML/time: Difference between revisions

Jump to navigation Jump to search
expanded time element and example has been fixed in WHATWG HTML
m (Added hyperlinks to <time> in the MDN.)
(expanded time element and example has been fixed in WHATWG HTML)
Line 10: Line 10:


== time element spec issues ==
== time element spec issues ==
=== nesting time ===
Recorded on WHATWG wiki:
* http://wiki.whatwg.org/wiki/Time_element#composite_nested_time_elements
* http://wiki.whatwg.org/wiki/Time_element#am_pm_and_coarser_time_parsing
for better DRY:
* improve <code>&lt;time&gt;</code> element to support uses analogous to the microformats "value class pattern" date and time separation use case (compose nested <code>&lt;time&gt;</code> elements into a single date and time) - and am pm handling
** 2010-08-10 emailed whatwg list: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027845.html
** perhaps even use a <code>&lt;time&gt;</code> to compose multiple nested date/time <code>&lt;input&gt;</code> elements for specific date/time components into a single date and/or time.
== time element resolved spec issues ==
=== expand time ===
=== expand time ===
* expand <code>&lt;time&gt;</code> and new date/time <code>[https://developer.mozilla.org/en/HTML/Element/time &lt;input&gt;]</code> elements to be consistent and reflect more real world use cases
* expand <code>&lt;time&gt;</code> and new date/time <code>&lt;input&gt;</code> elements to be consistent and reflect more real world use cases
** impedance match. handle the same set of year, month, date, time variants/subsets between the two. what is taken as input is nearly always displayed as output - the use cases are analogous/parallel.
** impedance match. expand time to handle the same set of year, month, date, time variants/subsets that input handles. what is taken as input is nearly always displayed as output - the use cases are analogous/parallel.
*** recorded/expanded on the WHATWG wiki: http://wiki.whatwg.org/wiki/Time_element#impedance_match_new_date_time_inputs
*** recorded/expanded on the WHATWG wiki: http://wiki.whatwg.org/wiki/Time_element#impedance_match_new_date_time_inputs
*** 2010-08-07 new related time element granularities all proposed here: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027722.html
*** 2010-08-07 new related time element granularities all proposed here: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027722.html
Line 22: Line 33:
*** 2010-08-07 posted more date granularity: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027722.html
*** 2010-08-07 posted more date granularity: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027722.html
*** 2010-08-08 posted more datetime [[HTML5/input|input]] types: http://wiki.whatwg.org/wiki/Input_element#new_date_time_inputs
*** 2010-08-08 posted more datetime [[HTML5/input|input]] types: http://wiki.whatwg.org/wiki/Input_element#new_date_time_inputs
=== nesting time ===
Recorded on WHATWG wiki:
* http://wiki.whatwg.org/wiki/Time_element#composite_nested_time_elements
* http://wiki.whatwg.org/wiki/Time_element#am_pm_and_coarser_time_parsing
for better DRY:
* improve <code>&lt;time&gt;</code> element to support uses analogous to the microformats "value class pattern" date and time separation use case (compose nested <code>&lt;time&gt;</code> elements into a single date and time) - and am pm handling
** 2010-08-10 emailed whatwg list: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027845.html
** perhaps even use a <code>&lt;time&gt;</code> to compose multiple nested date/time <code>&lt;input&gt;</code> elements for specific date/time components into a single date and/or time.


=== editorial example fix ===
=== editorial example fix ===
canmove, Confirmed users
2,675

edits

Navigation menu