[Calendar] Fix broken dates when keyboard typed

[prudho]

Description

This PR aim to fix (or at least drastically reduce) the broken date format when it's typed through keyboard. It's a bit hacky, since it only reverse supposed days and month when the setting monthFirst is defined to true, but I think this little piece of code will cover 98% of cases.

Testcase

Before: JSFiddle
After: JSFiddle

Closes

#829
#986

[lubber-de]

🤔 Isn't the change assuming the provided text is always in "wrong" order when monthFirst = false? It would exchange those two values all the time.
I think we should rather replace the whole parser by a proper method which always uses a given dateFormat setting without the need to rely on heavy extra libraries like moment.js

I think adopting something like the following tiny but effective method is suitable
http://blog.stevenlevithan.com/archives/date-time-format
->
https://github.com/felixge/node-dateformat/blob/master/lib/dateformat.js

[prudho]

For users who use the "dd/mm/yyyy" format, they'll type as it, so the date will be always be corrected for them. People that use monthFirst: false are, for the vast majority, the same people that use the "dd/mm/yyyy" format (let's say 98% 😃).

I know that it's not the best solution, but write a brand new date parser, which will handle all dates specificities (timezones, format...), will need a heavy reflection (and we must not forget that calendar can also handle minutes, month and years only).

[lubber-de]

Lets also support a dot as divider, otherwise it is still failing

[lubber-de]

LGTM
I also changed the jsfiddle with a new one to prove the dot usage is also fixed

[y0hami]

LGTM

[exoego]

LGTM

[PhilippGrashoff]

I also changed the jsfiddle with a new one to prove the dot usage is also fixed

Hi, I tested the jsFiddle https://jsfiddle.net/z6ghfcv9/, but its failing as in lubber_de's gif. It picks 12th of october if a dot is used as seperator

[lubber-de]

@PhilippGrashoff
😱 I confirm, it still happened when using at least Edge/IE11 ...
I created another Hotfix #1004 which should work in any browser now
Please try this new jsfiddle https://jsfiddle.net/9caf67pv/