Skip to content
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.tz.guess timezone is not correct at Chrome 61 #3418

Closed
chenlingmin opened this issue Sep 28, 2017 · 6 comments
Closed

moment.tz.guess timezone is not correct at Chrome 61 #3418

chenlingmin opened this issue Sep 28, 2017 · 6 comments

Comments

@chenlingmin
Copy link

chenlingmin commented Sep 28, 2017

Help me!
It's only in my computer Chrome browser.

actual time is 2017-09-28 19:12:16, and the time for the HTTP request and response is also this.
But url and chart time is 2017-09-28 06:12:16.

I don't know what happened☹️.
image

@chenlingmin chenlingmin changed the title What's wrong with this? moment.tz.guess is not correct At Chrome 61 Oct 10, 2017
@chenlingmin
Copy link
Author

chenlingmin commented Oct 10, 2017

in Chrome console, I exec moment.tz.guess(), is return "America/Chicago".
and in Safari, is return "Asia/Shanghai"

My Chrome version is 61.0.3163.100 (Official Build) (64-bit)

this is Chrome test console
image

this is Safari test console
image

@chenlingmin chenlingmin changed the title moment.tz.guess is not correct At Chrome 61 moment.tz.guess is not correct at Chrome 61 Oct 10, 2017
@chenlingmin chenlingmin changed the title moment.tz.guess is not correct at Chrome 61 moment.tz.guess timezone is not correct at Chrome 61 Oct 10, 2017
@denzelsN
Copy link
Contributor

Would you check your OS timezone?
moment's timezone check logic : https://momentjs.com/timezone/docs/#/using-timezones/guessing-user-timezone/

@chenlingmin
Copy link
Author

It is Asia/Shanghai

image

@denzelsN
Copy link
Contributor

It's like this issue. moment/moment-timezone#517
I'll check it out.

@chenlingmin
Copy link
Author

Yeah. 👍

@stale
Copy link

stale bot commented Jul 13, 2018

This issue/proposal has been automatically marked as stale because it hasn't had any recent activity. It will automatically be closed if no further activity occurs for 20days. If you think this should still be open, or the problem still persists, just pop a reply in the comments and one of the maintainers will (try!) to follow up. Thank you for your interest and contribution to the Pinpoint Community.

@stale stale bot added the stale label Jul 13, 2018
@stale stale bot closed this as completed Aug 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants