-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
p-calendar doesn't display correct date when utc="true" #3611
Comments
I was not able to replicate this issue, but I have another issue, using your plunker, timezone does not seem to be set to UTC even if UTC was set to true |
Looking at the source code for the calendar component, this is all the
It creates a local I was hoping that enabling UTC would allow the component to accept a UTC date input and then output the UTC date value in the control. |
To be fair, I have since discovered that displaying a formatted date specific to a timezone won't be possible until Angular v5: angular/angular#9324 It looks like he got his PR done though and it's ready to be merged: angular/angular#18284. So hopefully PrimeNG will build this capability into their calendar component when the time comes. |
Hey @cagataycivici , you closed my issue (#4179) as duplicate of this. I hope you noticed I linked a PR for it.. (#4180). |
Merged PR from @jonyadamit #4180 |
There is no guarantee in receiving a response in GitHub Issue Tracker, If you'd like to secure our response, you may consider PrimeNG PRO Support where support is provided within 4 business hours
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
http://embed.plnkr.co/heusWuPPLdRCOaG0u0AD/
Current behavior
When you select a date, the wrong value is shown in the field.
Expected behavior
The date selected will continue to be shown.
Minimal reproduction of the problem with instructions
See plunk
What is the motivation / use case for changing the behavior?
Visually the users need to see the date they chose, even if in UTC it's the day prior.
Please tell us about your environment:
N/A
Angular version: 2.0.X
4.2.6
PrimeNG version: 2.0.X
4.1.2
Browser: all
Language: all
Node (for AoT issues):
node --version
= N/AThe text was updated successfully, but these errors were encountered: