date entry bug if not fully keyed

[Richard deMeester]

Hello,

We have noticed a very annoying issue, and we are not sure if it is web, client or server related. We have our localisation set so that date formats are dd/mm/yy. Using Chrome and server / addons / web are up to date (as of a week ago, or so)

This problem occurs in date entries and datetime entries:

In datetime, if we enter the first value, we get the second

"03/10/12 12:03:05" -> "03/10/12 12:03:05" (correct)
"3/10/12 12:03:05" -> "10/03/12 12:03:05" (incorrect)
"03/10/12 12:03:5" -> "10/03/12 12:03:05" (incorrect)
"03/10/12 12:03" -> "10/03/12 12:03:00" (incorrect)

In date entries:
"03/01/12" -> "03/01/12" (correct)
"3/01/12" -> "01/03/12" (incorrect)

If any of the values is missing or is not specified with 2 digits, then the day and month get switched.

I don't know if this is the correct project to report this one.

Richard

[Florent (florent.x)]

The workaround is to add this snippet to the javascript part of a custom addon, until it is fixed upstream :

Date.parseExact = function(s, fx) {
    fx = fx.replace(/dd(.)MM/, 'd$1M');
    return Date.getParseFunction(fx)(s);
};

Tested on OpenERP 6.1 with French format (dd/MM/yyy) and Swiss format (dd.MM.yyyy).

[Florent (florent.x)]

I verified that the bug is present in OpenERP 6.1 and OpenERP 7.0.

It seems fixed in trunk, though.