-
Notifications
You must be signed in to change notification settings - Fork 68
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
Use the browser's timezone by default #22
Use the browser's timezone by default #22
Conversation
|
||
setCookie(mode); | ||
setCookie('true', 'local'); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me!
if (mode == 'local') { | ||
options[mode].checked = true; | ||
mode = 'system'; | ||
} | ||
modes[mode].checked = true; | ||
|
||
// Renew the cookie. | ||
setCookie(mode); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure this should have been removed? It was there to auto-renew the cookie, so that it only expires if the page has not been visited in 2 years as in https://googleblog.blogspot.com.au/2007/07/cookies-expiring-sooner-to-improve.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated, thanks.
Previously, we would default to 'system clock time' when no cookies were set. Users would see UTC time unless they explicitly opted in to the browser timezone. This only impacts new users, or when the cookie expires.
b8b594f
to
b403d8e
Compare
Thanks! |
Fixed included in Timestamper 1.8.10 which will be available shortly. |
Previously, we would default to 'system clock time' when no cookies
were set. Users would see UTC time unless they explicitly opted in to
the browser timezone.
This only impacts new users, or when the cookie expires.