manually entered date not parsed correctly by datepicker

[terebentina]

When you pick a date with the datepicker, it correctly shows the picked date in the input field, properly formatted as specified by the datepicker-popup format.

In my case I used datepicker-popup="dd/MM/yyyy" (note the month is the second, day is first)

So if I pick November 1st, 2013 then the input would show 01/11/2013 (correct so far).

However, if I delete the date in the input field and start typing the exact same date, the date picker goes to January 11th, 2013 - it thinks month is first.

By looking at the code I see there's no attempt to parse the value according to the format - the entered value is passed directly to Date().

Plunker for this: http://plnkr.co/edit/uibdoKRTMHLxJJy3KbMS?p=preview but it's basically the default datepicker, nothing special done there.

[pkozlowski-opensource]

@terebentina the problem is that JavaScript is not able to parse custom-formated dates so we would have to add dependency on a 3rd party library, like moment.js, and write a custom parser. I'm keeping this issue around to update docs with more info. We might also try to provide a separate directive that would have dependency on moment.js and work with all date formats suported by moment.js.

[terebentina]

Yeah, I figured it might be the case. However, please note that it's very disconcerting to delete the date from the field and enter the same thing again just to see it jump to another date.
So much so that I think there's no much point in using an input field if it's parsed wrongly. I'd much rather have just the popup trigger button and show the date in a span or something.

I haven't decided what to do about this for my project yet. If I decide to fork and try using moment.js for this I will send you a PR.
I am thinking that checking if moment() exists and using that to parse the date, otherwise keep the default behavior would be minimally invasive. What do you think?

[molerat619]

Any news on this?