Menu
One of the new changes being introduced in HTML5 is the support for date/time as a first class input element type. The introduction of this new input type allows web developers to get the input element's value as a string which represents date/time. There are two input types supported for “datetime” like inputs. 2.
Time: The time input type of HTML5 enables the user to select only time from the time picker. Datetime local: It is used to select date and time and it represents input date-time value as local time. Month: This attribute also shows a calendar to the user, but the user can select only a month from the calendar.
When you view a new HTML5 form input type in an older browser, most of the browsers both old and the new can handle the HTML elements even they are unrecognized as input elements. But as a user, you can make the browser to identify and handle those input types.
The only reason I can think of is browser vendors losing faith in the standard being approved, therefore removing the implementation from their code.
To support this thought: W3C just removed both datetime and datetime-local from their working draft.
Browser vendors will eventually drop support of both of them.
According to html5test most of the current browsers removed support of both of the input types.
The latest development:
datetime-local is back on the draft;datetime, but it does show datetime-local. It does sound like it is back on the map and going to be supported again!Also take notice of this related post on Webmasters.SE: Is datetime-local removed from HTML 5.1?.
Source http://www.w3.org/TR/html5/
"The following features are at risk and may be removed due to lack of implementation.
..<input type=datetime>.."
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With