HTML/time: Difference between revisions
< HTML
Jump to navigation
Jump to search
(→expand time: impedance match time and datetime inputs proposed) |
|||
| Line 14: | Line 14: | ||
** 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. 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. | ||
*** 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-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/[[HTML5/input|input]] to handle additional real world cases, e.g.: YYYY and --MM-DD | ** more inputs/times. expand both time/[[HTML5/input|input]] to handle additional real world cases, e.g.: YYYY and --MM-DD | ||
*** recorded/expanded on the WHATWG wiki: | *** recorded/expanded on the WHATWG wiki: | ||
Revision as of 22:33, 9 August 2010
Welcome to the Mozilla wiki page on the HTML5 <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
expand time
- expand
<time>and new date/time<input>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.
- 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
- 2010-08-08 posted more datetime input types: http://wiki.whatwg.org/wiki/Input_element#new_date_time_inputs
- 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.
nesting time
Recorded on WHATWG wiki: http://wiki.whatwg.org/wiki/Time_element#composite_nested_time_elements
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)- 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.
- perhaps even use a
see also
- HTML5 home page