parseZone() not parsing UTC correctly

[sebastien-ma]

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.

[maggiepint]

Yep. That's wrong. I'll maybe see if I can't tackle that one tonight, I think I know where it happened.

[tlrobinson]

FYI this bug was introduced in the fix for #3083, b2ee2d4

[mfn]

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

[wi-ski]

PR handles the issue I believe - #3504 - Please let me know if its just flat wrong. @maggiepint

[mfn]

I can confirm that it fixes my problem from #3463 (comment)

[wi-ski]

#3504 just got labeled a bug fix w00t!