New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moment().toISOString(true) is not keep the local time #4390

Closed
lira92 opened this Issue Jan 4, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@lira92

lira92 commented Jan 4, 2018

When I execute moment().toISOString() the result is "2018-01-04T12:54:33.621Z" and when I execute moment().toISOString(true) the result is "2018-01-04T12:54:35.916-02:00", Shouldn't be "2018-01-04T10:54:35.916-02:00" ?

Environment:
Chrome 63.0.3239.108 on Windows 10 64 bit

The time and date at which the code was run
2018-01-04 10:54:35 (America/São Paulo)

If you are reporting an issue, please run the following code in the environment you are using and include the output:

Thu Jan 04 2018 11:02:16 GMT-0200 (Horário brasileiro de verão)
04/01/2018 11:02:16
120
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
2.20.1

ashsearle added a commit to ashsearle/moment that referenced this issue Jan 4, 2018

@ashsearle

This comment has been minimized.

Contributor

ashsearle commented Jan 4, 2018

My mistake... should be fixed by PR #4391

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment