Re: [qooxdoo-devel] qooxdoo 3.0.x : Error parsing (valid) date ...

[Thomas H. <tho...@1u...>]

Peter,

please open a bug an attach your patch there.

Thanks,
T.

On Fri, 29 Nov 2013 16:51:38 +0100, Peter Schneider
<p.s...@ti...> wrote:
> The attached patch seems to fix the issue!
> And still checks whether "the value for day or month is too large".
> 
> /Peter
> 
> On 11/29/2013 2:01 PM Peter Schneider wrote:
>> Hi again,
>> 
>> the problem seems to be even worse :(
>> 
>> The offset calculation seems to be entirely wrong...
>> 
>> <code>
>>   var fmt = new qx.util.format.DateFormat("isoUtcDateTime");
>>   var ddd = fmt.parse("2004-04-04T04:04:04Z");
>>   ddd.getUTCHours(); // This does NOT return 4 !!!
>> </code>
>> 
>> Either I am completely confused, or there is some issue in that
>> formatter/parser
>> (seems to be that the UTC-offset is added instead of subtracted
>>  ...or the other way around)
>> 
>> /Peter
>> 
>> 
>> 
>> On 11/29/2013 11:55 AM Peter Schneider wrote:
>>> Hi qooxdoo-devs,
>>>
>>> the current implementation of qx.util.format.DateFormat is not able to
>>> parse
>>> "isoUtcDateTime" when it comes to a 'year-change' due to timezone
offset
>>> (GMT+1)
>>>
>>>
>>> Following example...
>>>
>>> <code>
>>> (new
>>>
qx.util.format.DateFormat("isoUtcDateTime")).parse("2013-01-01T00:00:00Z")
>>> </code>
>>>
>>> ...throws the following exception:
>>>
>>>   Error: Error parsing date '2013-01-01T00:00:00Z': the value for day
>>>   or month
>>>          is too large
>>>
>>>
>>>
>>> Due to the fact that most of my clients are at GMT+1, I hope this gets
>>> fixed
>>> before New Year's Eve :)
>>>
>>> /Peter
>>>
>>>
>>> P.S.: Do you think it is needed to open a bug-report for this?
>>>