#15125 closed bug (cantfix)

Opened January 06, 2017 03:35PM UTC

Closed January 11, 2017 01:21AM UTC

datepicker.parseDate return incorrect date on Firefox (date parsed -1)

Reported by:	rodriformiga	Owned by:	rodriformiga
Priority:	minor	Milestone:	none
Component:	ui.datepicker	Version:	1.12.1
Keywords:		Cc:
Blocked by:		Blocking:

Description

Here is an example:

Var ret = $ .datepicker.parseDate ("dd / mm / yy", "03/01/2016")
Console.log(ret);  //this return Day 02 and not Day 03

NOTE: If you use the ret.getDate () function, the returned day is correct.

Ex: https://jsfiddle.net/rodriformiga/mxhejz2h/

Attachments (0)

Change History (4)

Changed January 06, 2017 03:52PM UTC by rjollos comment:1

description:	By running a parse function in updated Firefox, the returned date gets the day -1. This bug has been identified only in Firefox. In Chrome and IE works perfectly. Testing with other date formats was also performed, but the problem persists. \ Here is an example: \ \ Var ret = $ .datepicker.parseDate ("dd / mm / yy", "03/01/2016") \ Console.log(ret); //this return Day 02 and not Day 03 \ \ NOTE: If you use the ret.getDate () function, the returned day is correct. \ \ Ex: https://jsfiddle.net/rodriformiga/mxhejz2h/ → By running a parse function in updated Firefox, the returned date gets the day -1. This bug has been identified only in Firefox. In Chrome and IE works perfectly. Testing with other date formats was also performed, but the problem persists. \ Here is an example: \ \ {{{#!javascript \ Var ret = $ .datepicker.parseDate ("dd / mm / yy", "03/01/2016") \ Console.log(ret); //this return Day 02 and not Day 03 \ }}} \ \ NOTE: If you use the `ret.getDate ()` function, the returned day is correct. \ \ Ex: https://jsfiddle.net/rodriformiga/mxhejz2h/

description:

By running a parse function in updated Firefox, the returned date gets the day -1. This bug has been identified only in Firefox. In Chrome and IE works perfectly. Testing with other date formats was also performed, but the problem persists. \ Here is an example: \ \ Var ret = $ .datepicker.parseDate ("dd / mm / yy", "03/01/2016") \ Console.log(ret); //this return Day 02 and not Day 03 \ \ NOTE: If you use the ret.getDate () function, the returned day is correct. \ \ Ex: https://jsfiddle.net/rodriformiga/mxhejz2h/ → By running a parse function in updated Firefox, the returned date gets the day -1. This bug has been identified only in Firefox. In Chrome and IE works perfectly. Testing with other date formats was also performed, but the problem persists. \ Here is an example: \ \ {{{#!javascript \ Var ret = $ .datepicker.parseDate ("dd / mm / yy", "03/01/2016") \ Console.log(ret); //this return Day 02 and not Day 03 \ }}} \ \ NOTE: If you use the `ret.getDate ()` function, the returned day is correct. \ \ Ex: https://jsfiddle.net/rodriformiga/mxhejz2h/

Changed January 06, 2017 08:56PM UTC by scottgonzalez comment:2

owner:	→ rodriformiga
status:	new → pending

I can't reproduce this behavior using Firefox 50.1.0 on OS X 10.12.2. Also, if ret.getDate() is returning the correct value, it sounds like the date object is correct and there's nothing we can do about this.

Changed January 09, 2017 03:33PM UTC by rodriformiga comment:3

status:	pending → new

I reproduce in Firefox 50.1.0 and Firefox 47.0.1, both on Windows 8.1 x64.

Changed January 11, 2017 01:21AM UTC by scottgonzalez comment:4

resolution:	→ cantfix
status:	new → closed

I can't reproduce using Firefox 50 on Win 8.1: https://cloudup.com/cHL5OQZaMc3

Again, if ret.getDate() is returning the correct value, it sounds like the date object is correct and there's nothing we can do about this. Even though this works for me, I'm going to close as can't fix.

Search and Top Navigation