HTML/time: Difference between revisions
< HTML
(HTML) |
|||
| (13 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Welcome to the Mozilla wiki page on the [[ | Welcome to the Mozilla wiki page on the [[HTML]] [https://developer.mozilla.org/en/HTML/Element/time <time>] element. Please feel free to contribute new test pages or new sections. -- [[User:Tantek|Tantek]] | ||
{{stub}} | {{stub}} | ||
| Line 10: | Line 10: | ||
== time element spec issues == | == time element spec issues == | ||
=== nesting time === | === 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: | for better DRY: | ||
* improve <code><time></code> element to support uses analogous to the microformats "value class pattern" date and time separation use case (compose nested <code><time></code> elements into a single date and time) | * improve <code><time></code> element to support uses analogous to the microformats "value class pattern" date and time separation use case (compose nested <code><time></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><time></code> to compose multiple nested date/time <code><input></code> elements for specific date/time components into a single date and/or time. | ** perhaps even use a <code><time></code> to compose multiple nested date/time <code><input></code> elements for specific date/time components into a single date and/or time. | ||
== time element resolved spec issues == | |||
=== expand time === | |||
* expand <code><time></code> and new date/time <code><input></code> elements to be consistent and reflect more real world use cases | |||
** 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 | |||
*** 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-09 impedance match email to whatwg: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027773.html | |||
** more inputs/times. expand both time/[[HTML/input|input]] to handle additional real world cases, e.g.: YYYY and --MM-DD | |||
*** recorded/expanded on the WHATWG wiki: | |||
**** http://wiki.whatwg.org/wiki/Time_element#impedance_match_new_date_time_inputs | |||
**** http://wiki.whatwg.org/wiki/Input_element#new_date_time_inputs | |||
*** 2010-08-07 posted more date granularity: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027722.html | |||
=== editorial example fix === | |||
Recorded on WHATWG wiki: | |||
* http://wiki.whatwg.org/wiki/Time_element#Update_hCalendar_example | |||
Posted to WHATWG list: | |||
* http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027894.html | |||
== see also == | == see also == | ||
* [[ | * [[HTML]] home page | ||
Latest revision as of 07:56, 20 July 2018
Welcome to the Mozilla wiki page on the HTML <time> element. Please feel free to contribute new test pages or new sections. -- Tantek
This article is a stub. You can help MozillaWiki by expanding it.
time element test pages
- ...
time element demo pages
- ...
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
<time>element to support uses analogous to the microformats "value class pattern" date and time separation use case (compose nested<time>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
<time>to compose multiple nested date/time<input>elements for specific date/time components into a single date and/or time.
time element resolved spec issues
expand time
- expand
<time>and new date/time<input>elements to be consistent and reflect more real world use cases- 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
- 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-09 impedance match email to whatwg: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027773.html
- more inputs/times. expand both time/input to handle additional real world cases, e.g.: YYYY and --MM-DD
- recorded/expanded on the WHATWG wiki:
- 2010-08-07 posted more date granularity: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027722.html
- 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.
editorial example fix
Recorded on WHATWG wiki:
Posted to WHATWG list:
see also
- HTML home page