-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(datepicker): force Intl.DateTimeFormat to use UTC time zone ... #5747
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
Conversation
doesn't display incorrect dates.
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.
LGTM
@mmalerba seems like there's a linting error and the output format is different on iOS Safari. |
lint + tests fixed |
date = new Date(Date.UTC( | ||
date.getFullYear(), date.getMonth(), date.getDate(), date.getHours(), | ||
date.getMinutes(), date.getSeconds(), date.getMilliseconds())); | ||
displayFormat = Object.assign({}, displayFormat, {timeZone: 'utc'}); |
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.
@mmalerba Object.assign
is breaking in Google. Can you switch to our util extendObject
?
fixed |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
so it doesn't display incorrect dates.
fixes #5185
@julianobrasil Thanks for tracking down the root issue!