pb with displaying events (DST issue)
See original GitHub issueDescribe the bug Hi. Found issue when displaying slots on calendar on 25th of October for Europe/London (for instance). Same issue on your demo https://angular-calendar.com/#/kitchen-sink, try to add event on 25th of October
Can you fix it?
Thx.
Minimal reproduction of the problem with instructions
Screenshots
Versions
@angular/core
: 10.1.4angular-calendar
: 0.28.20- Browser name and version: all
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Problem with UTC and daylight savings time?
I've worked it out. If I set the Sharepoint list time zone to anything except UK (so BST, shows as UTC +0) then...
Read more >DST issues in Calendar [36910070] - Visible to Public
The expected behavior is that the event shows up at 5:30 each time, regardless of whether DST is in effect. This issue can...
Read more >Issues with Daylight Savings settings & exporting events to ...
If the “This event is effected by day light savings time” setting is de-activated, it shows the wrong time during the Daylight Savings...
Read more >Inconsistent time stamp for events date during DST
The timestamp calculated in the events grid have Daylight Saving Time applied, while the time zones and timestamps displayed in the dropdown ...
Read more >macOS Calendar DST Change Problem - Apple Community
MacBook Pro with Retina display, macOS Sierra (10.12.2), null ... I am here in Lisbon, too, and I don't see the same problem....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mattlewis92 issue fixed, thx a lot 😃
Should be fixed now in
0.28.21
, thanks for letting me know! 😄