You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Currently, for example, input[datetime-local] requires the input to be in the format yyyy-MM-ddTHH:mm:s (documentation for input[datetime-local]) which in most cases is useless for end users.
The date/time inputs should allow custom formatting (while the model remains a Date object).
The text was updated successfully, but these errors were encountered:
PawelDecowski
changed the title
Allow human-friendly date/time formats in input[type=date] and input[type=datetime-local]
Allow human-friendly date/time formats in input[date] and input[datetime-local]
May 8, 2015
I agree that the current state is not pretty. I think this could be a good fit for a third-party module, though (implemented via parsers / formatters):
browser support is still fragmented for the date input, so many people will still use full fledged date pickers. Then again, chrome already has a date picker
there are many different date formats, multiplied by locales. This would be a heavy burden on the core
Currently, for example,
input[datetime-local]
requires the input to be in the formatyyyy-MM-ddTHH:mm:s
(documentation forinput[datetime-local]
) which in most cases is useless for end users.The date/time
input
s should allow custom formatting (while the model remains aDate
object).The text was updated successfully, but these errors were encountered: