Date parse issue with "m/Y" format

**Daniil** · 31 Jan 2013 10:13 PM

REQUIRED INFORMATION

Ext version tested:

Ext 4.2.0 beta 2

Browser versions tested against:

Chrome
IE9

DOCTYPE tested against:

<!DOCTYPE html>

Description:

A date string is incorrectly parsed upon some conditions:

Format - "m/Y"
Current OS date - 29-31 January inclusive
Parsed date - some from February

The date is parsed as "03/2013"

Steps to reproduce the problem:

Set up the current OS date to some from 29-31 January inclusive.
Select some February date in the field
Blur the field

The result that was expected:

"02/2013"

The result that occurs instead:

"03/2013"

Test Case:

Code:

<!DOCTYPE html>
<html>
<head>
    <title>Date parser issue m/Y</title>

    <link rel="stylesheet" href="../resources/css/ext-all.css" />
    
    <script src="../ext-all-debug.js"></script>

    <script>
        Ext.onReady(function () {
            Ext.create("Ext.form.field.Date", {
                renderTo: Ext.getBody(),
                format: "m/Y"    
            });
        });
    </script>
</head>
<body>

</body>
</html>

**mankz** · 1 Feb 2013 4:18 AM

Probably same issue as this old one: http://www.sencha.com/forum/showthre...l=1#post145621

**Daniil** · 3 Feb 2013 10:42 PM

Thank you for the answer! I will investigate the thread.

Just a quick question: do you agree it is a bug and should be fixed?

**Daniil** · 11 Feb 2013 12:02 AM

Originally Posted by Daniil

Thank you for the answer! I will investigate the thread.

Yes, it looks to be the same issue.

Could you answer this? Just to know your opinion.

Originally Posted by Daniil

Just a quick question: do you agree it is a bug and should be fixed?

**mankz** · 12 Feb 2013 12:02 AM

Well, possibly yes. It would make sense for

Code:

Ext.Date.format(new Date(), 'M Y')

To produce consistent result regardless of the current date. We'll have to wait for the Ext devs to chime in.

**Daniil** · 5 Mar 2013 10:57 PM

Bump...

Could someone from ExtJS team kindly look at this issue?

**Animal** · 9 Mar 2013 6:10 PM

So that should create time 00:00:00 on the 1st of that month?

**Animal** · 9 Mar 2013 6:42 PM

I can't reproduce the OP's problem with latest code.

I just set my machine's date to 31st March.

And his code produces "02/2013" when selecting a date in Feb.

**Daniil** · 11 Mar 2013 7:27 AM

@Animal, thank you for the answer!

Originally Posted by Animal

So that should create time 00:00:00 on the 1st of that month?

Probably, yes.

Originally Posted by Animal

And his code produces "02/2013" when selecting a date in Feb.

Yes, it produces "02/2013" on selecting a date, but it becomes "03/2013" on bluring.

Please clarify did you blur the field?

**Animal** · 11 Mar 2013 8:05 AM

I did, but I probably had the wrong conditions set up.

Evan has put in a fix for this.

When defaulting in a day number when one has not been specified in the string, it minimizes the default day number with <lastDayInCurrentMonth>

So this one is fixed.

Date parse issue with "m/Y" format

Thread Tools

Search Thread

Display

Date parse issue with "m/Y" format

Date parse issue with "m/Y" format