Moment: parseZone() not parsing UTC correctly
On latest version (2.15.1), parseZone() seems not working correctly when offset is utc.
moment.parseZone('2016-05-04T00:00:00Z').format()
=> "2016-05-04T08:00:00Z" bad
moment.parseZone('2016-05-04T00:00:00+08:00').format()
=> "2016-05-04T00:00:00+08:00" good
The method was good on 2.14.1, I recently updated moment.js to 2.15.1 and the new version failed my test case.
sebastien-ma
All 6 comments
Yep. That's wrong. I'll maybe see if I can't tackle that one tonight, I think I know where it happened.
maggiepint
on 23 Sep 2016
FYI this bug was introduced in the fix for #3083, b2ee2d444282fcb90abfd43fe562253c73e14b08
tlrobinson
on 5 Oct 2016
Is this maybe related? I tested with with 2.15.1 too:
t = moment().toISOString();
console.log(t.toString());
parsed = moment.parseZone(t);
console.log(parsed.toISOString());
Outputs:
2016-10-14T15:33:37.457Z
2016-10-14T17:33:37.457Z
My local time is "Europe/Vienna" and thus I know where the 2 hour difference probably comes from but I don't see why it should do it.
With 2.14.1 I get the expected output:
2016-10-14T15:36:23.956Z
2016-10-14T15:36:23.956Z
mfn
on 14 Oct 2016
PR handles the issue I believe - #3504 - Please let me know if its just flat wrong. @maggiepint
wi-ski
on 14 Oct 2016
I can confirm that it fixes my problem from https://github.com/moment/moment/issues/3463#issuecomment-253836488
mfn
on 14 Oct 2016
3504 just got labeled a bug fix w00t!
wi-ski
on 15 Oct 2016
Related issues
ninigix
·
3Comments
slavafomin
·
3Comments
4rg0n
·
3Comments
paulyoung
·
3Comments
benhathaway
·
3Comments
Most helpful comment
3504 just got labeled a bug fix w00t!