Probably bug in RelativeDateItem – time value of CalculatedDateField

[geletkaf]

Hi,

using 3.1p.2012-11-25 with Firefox 16.0.

Problem: CalculatedDateField (part of RelativeDateItem) shows unexpected time value.

Windows settings:
Timezone: (UTC-06:00) Central Time (US & Canada)
DST activated (Automatically adjust clock for Daylight Saving Time)

Globally set:

DateUtil.setDefaultDisplayTimezone("+01:00"); // emulates (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna

Item used in Dynamicform:

RelativeDateItem test = new RelativeDateItem("test");
test.setType(FieldType.DATETIME.getValue());

-------------------------------------------------------------------------------------------
Use case 1:

DateUtil.setAdjustForDST(true);

Typed into field: 03/30/2012 09:00:00
Shows Calculated Value: 03/30/2012 02:00:00 -> wrong?
Send to the server (after submitting form): 2012-03-30T07:00:00

Typed into field: 03/20/2012 09:00:00
Shows Calculated Value: 03/20/2012 02:00:00 -> wrong?
Send to the server (after submitting form): 2012-03-20T07:00:00

Typed into field: 03/10/2012 09:00:00
Shows Calculated Value: 03/10/2012 02:00:00 -> wrong?
Send to the server (after submitting form): 2012-03-10T08:00:00

-------------------------------------------------------------------------------------------
Use case 2:

DateUtil.setAdjustForDST(false);

Typed into field: 03/30/2012 09:00:00
Shows Calculated Value: 03/30/2012 03:00:00 -> wrong?
Send to the server (after submitting form): 2012-03-30T08:00:00

Typed into field: 03/20/2012 09:00:00
Shows Calculated Value: 03/20/2012 03:00:00 -> wrong?
Send to the server (after submitting form): 2012-03-20T08:00:00

Typed into field: 03/10/2012 09:00:00
Shows Calculated Value: 03/10/2012 02:00:00 -> wrong?
Send to the server (after submitting form): 2012-03-10T08:00:00

Is it a bug? If yes, when can be solved?

[Isomorphic]

As it happens, we just fixed a bug that probably has the same underlying cause. Can you test with the latest nightly patch build?