On Wednesday, March 22, 2017 at 7:31:11 AM UTC+8, Karl Dubost wrote: > Eric, > > Le 21 mars 2017 à 23:38, Eric Shepherd <esheph...@mozilla.com> a écrit : > > We’re updating the <input> element’s documentation to not suck (yay!) > > Thanks! > > Test: http://codepen.io/webcompat/pen/bqvarY (datetime, datetime-local) > Results: http://imgur.com/a/q9cNr (Gecko, Blink, WebKit) > > Summary: only Blink provides (as of now) a datetime-local type with a > specific UI. > > Comment 93 gives plenty of followup bugs for the future of this input. > https://bugzilla.mozilla.org/show_bug.cgi?id=825294#c93 > > > -- > Karl Dubost, mozilla 💡 Webcompat > http://www.la-grange.net/karl/moz
WHATWG has dropped support for input type=datetime [1] in favor of using type=datetime-local with a separate drop-down for the time zone (or some similar UI). W3C still has concerns about input type=datetime-local [2], thou I'm not sure what the final consensus is. As for browser support, Chrome, Opera, and Microsoft Edge support type=datetime-local but not type=datetime. Firefox supports type=datetime-local, but it is under the pref "dom.forms.datetime.others", and has no specific UI for it yet (it's just a normal text box). A detailed plan for shipping each of the date/time input types with specific UI in Firefox can be found here [3]. [1] https://github.com/whatwg/html/issues/336 [2] https://lists.w3.org/Archives/Public/public-html/2014Feb/0003.html [3] https://wiki.mozilla.org/TPE_DOM/Date_time_input_types#Roadmap _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
