You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug which template:
[√ ] MaterialDesignFrameworkModule — Material Design
Bootstrap3FrameworkModule — Bootstrap 3
Bootstrap4FrameworkModule — Bootstrap 4
NoFrameworkModule — plain HTML
Other (please specify below)
A clear and concise description of what the bug is.
Previous issue #35 Commit#5c180bd
Dear @Benjitos, @hamzahamidi. This above commit doesn't resolve the date issue in different time zones. For my local system, it's working fine. After deploying the app in EC2 instance, the date behaves as shown in the following video. Please check it here: https://youtu.be/D0iwFov4t7Q
Scenario:
Let's say if I select a date as 14th, the displayed date will be 12th, but the date in the model(data) will be 13th
Initially, after your last commit, I updated my package to v7.0.1, this issue seems to be solved in my local date settings. But after deploying in the client environment, I still got this issue intact.
To Reproduce
Steps to reproduce the behavior:
Setup the library in an Angular v6 app as specified in the docs.
Used material design framework.
Defined schema and layout for the form.
From my timezone in IST, I changed my system timezone to CST(Chicago)[Indian Standard Time is 11 hours and 30 minutes ahead of Central Time]
The date type form field, which on selecting a date will go 1 day backward. For e.g., if I select 9Nov2018, it will be set in the form as 8Nov2018.
Expected behavior
On selecting a date from the date picker, it should set a correct selected date in the form.
Desktop (please complete the following information):
OS: [MacOS, Windows]
Browser [ chrome, safari]
Version [12, 70.0.3538.77]
Additional context
I think the time is being saved with default timezones and we should consider generalizing the date across all the timezones. Material datepicker has this issue.
Context
This change is really important because we have an application that requires a lot of dates and the dates are being set 1~2 day backward by using this form from different timezones.
@hamzahamidi , I know you are busy, but can you please comment on this.
The text was updated successfully, but these errors were encountered:
sai7
changed the title
Re-Posting the issue with DatePicker. Issue #35.
Re-Posting the issue with DatePicker. Issue #35. Date selected is displaying 2(two) days backwards in different time zones.
Dec 21, 2018
Describe the bug
which template:
[√ ] MaterialDesignFrameworkModule — Material Design
Bootstrap3FrameworkModule — Bootstrap 3
Bootstrap4FrameworkModule — Bootstrap 4
NoFrameworkModule — plain HTML
Other (please specify below)
A clear and concise description of what the bug is.
Previous issue #35
Commit# 5c180bd
Dear @Benjitos, @hamzahamidi. This above commit doesn't resolve the date issue in different time zones. For my local system, it's working fine. After deploying the app in EC2 instance, the date behaves as shown in the following video. Please check it here: https://youtu.be/D0iwFov4t7Q
Scenario:
Let's say if I select a date as 14th, the displayed date will be 12th, but the date in the model(data) will be 13th
Initially, after your last commit, I updated my package to v7.0.1, this issue seems to be solved in my local date settings. But after deploying in the client environment, I still got this issue intact.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
On selecting a date from the date picker, it should set a correct selected date in the form.
Desktop (please complete the following information):
OS: [MacOS, Windows]
Browser [ chrome, safari]
Version [12, 70.0.3538.77]
Additional context
I think the time is being saved with default timezones and we should consider generalizing the date across all the timezones. Material datepicker has this issue.
Context
This change is really important because we have an application that requires a lot of dates and the dates are being set 1~2 day backward by using this form from different timezones.
@hamzahamidi , I know you are busy, but can you please comment on this.
The text was updated successfully, but these errors were encountered: