datefield unusable in safari and locale nl_BE and nl_NL

[guyvanbael]

Affected Version: ss 4

• no datepicker is showing up in safari
• when contentlocal is nl_NL or nl_BE any selected date doesn't pass validation. It is always considered not a valid date. The form can't be submitted which is a real dealbreaker...

[guyvanbael]

same thing on de_DE
silverstripe/silverstripe-userforms#829 (comment)

[DorsetDigital]

The first part of the issue isn't directly a SS problem. SS4 uses a native HTML5 input for dates, and I don't believe that Safari actually renders one. You may need to use a plugin such as the silverware calendar to get around that part.

[guyvanbael]

IMHO something like this should have some kind of fallback for browsers that don't support this.
Dates show up in every website....
And as for the second issue... that's even a bigger problem for multilingual sites...

[guyvanbael]

it's probably an issue for userforms, because using the datefield in the cms is working as expected (except for the fact that safari is not rendering a datepicker)

[chillu]

The idea was that the fallback is a text field. We're not going to deal with a JS library for date picking on top of the increasingly native capabilities, that's been a conscious decision during 4.x development. But we need to ensure authors know what format to use to write a date into a text field (e.g. no ambiguity around short vs. long month names)

[lerni]

related: #7955
https://caniuse.com/#feat=input-datetime

[chillu]

@bergice Do you think this is still an issue?

[bergice]

@chillu The validation issue should be resolved (silverstripe/silverstripe-userforms#829 (comment)) and I can't replicate it.

Also looks like we won't be adding a datepicker library so I'm closing this.