Skip to content
This repository was archived by the owner on Sep 5, 2024. It is now read-only.

datepicker: ng-model-options timezone option not handled properly #10971

Closed
JohnPlaisted opened this issue Nov 6, 2017 · 1 comment
Closed
Assignees
Labels

Comments

@JohnPlaisted
Copy link

JohnPlaisted commented Nov 6, 2017

Actual Behavior:

  • What is the issue?
    The text for the date is correct but the date doesn't show up correctly in the Calendar. For me the date selected in the calendar is one day behind. I think this would be the case for users with a local time zone east of UTC. (a negative offset)
  • What is the expected behavior?
    The dates should match

CodePen (or steps to reproduce the issue): *

AngularJS Versions: *

  • AngularJS Version: 1.5.5
  • AngularJS Material Version: 1.1.5

Additional Information:

  • Browser Type: Firefox, Chrome
  • Browser Version: 56.0.2 , 61.0.3163.100
  • OS: Windows 7
  • Stack Traces:
@Splaktar Splaktar changed the title Incorrect date in Calendar datepicker: ng-model-options timezone option not handled properly Dec 27, 2017
@Splaktar Splaktar added type: bug i18n: localization This issue is related to internationalization needs: investigation The cause of this issue is not well understood and needs to be investigated by the team or community P3: important Important issues that really should be fixed when possible. ux: integration labels Dec 27, 2017
@Splaktar Splaktar added this to the 1.1.6 milestone Dec 27, 2017
@angular angular deleted a comment from SocVi100 Jan 5, 2018
@Splaktar Splaktar removed this from the 1.1.6 milestone Jan 5, 2018
@Splaktar Splaktar self-assigned this Jan 5, 2018
@Splaktar
Copy link
Contributor

Splaktar commented Jan 5, 2018

Thank you for your contribution!

This is a duplicate of #10598.

@Splaktar Splaktar closed this as completed Jan 5, 2018
@Splaktar Splaktar added resolution: duplicate and removed needs: investigation The cause of this issue is not well understood and needs to be investigated by the team or community P3: important Important issues that really should be fixed when possible. labels Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants