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
I am using silverstripe/blog, and notice that I do not get a dialog to fill in the PublishDate. The input uses type datetime-local, but this is not supported in Firefox (it's only supported in Chrome and Edge). The input says "03/26/2018 3:01 AM", and I can in fact update it if I use the same format, but that's not a native format to me, so I'm not sure where it's coming from. Perhaps it is a fallback mechanism using php interpretation?
I do notice that it has a hidden field which stores the actual PublishDate, and another field that is visible, so I guess there's javascript going on as well. So my suggestion is to check for browser support for datetime(-local), and if it's not there, separate the date and time into two inputs, and merge them together into the hidden input.
Any case, right now, it is a confusing experience.
The text was updated successfully, but these errors were encountered:
JorisDebonnet
changed the title
DatetimeField not supported in Firefox
DatetimeField not supported in Firefox or IE
Mar 26, 2018
Firefox has implement HTML5 date and HTML5 time fields, but not datetime (Chrome and Edge have datetime support). I agree that it's an issue, although I was hoping that Firefox simply took some time to catch up with other browsers, but there's been no movement on the bug report in five months...
I think for now, set your i18n.date_format and i18n.time_format to values that your authors can type out (e.g. not am/pm). We've invested weeks of dev time into i18n in SilverStripe 4 already, I don't think this will come up on our backlog soon.
Affected Version
4.1.0
Description
I am using silverstripe/blog, and notice that I do not get a dialog to fill in the PublishDate. The input uses type datetime-local, but this is not supported in Firefox (it's only supported in Chrome and Edge). The input says "03/26/2018 3:01 AM", and I can in fact update it if I use the same format, but that's not a native format to me, so I'm not sure where it's coming from. Perhaps it is a fallback mechanism using php interpretation?
I do notice that it has a hidden field which stores the actual PublishDate, and another field that is visible, so I guess there's javascript going on as well. So my suggestion is to check for browser support for datetime(-local), and if it's not there, separate the date and time into two inputs, and merge them together into the hidden input.
Any case, right now, it is a confusing experience.
The text was updated successfully, but these errors were encountered: