[MGNLUI-4153] DateColumnFormatter cannot handle DST correctly Created: 22/Feb/17 Updated: 30/Sep/21 Resolved: 30/Sep/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | workbench |
| Affects Version/s: | 6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | y2k | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
The DateFieldFactory, which is used to create the datepicker, defaults correctly against the SERVER-timezone, if no timezone is specified: (TimeZone is null in my case.) The DateColumnFormatter on the other hand, defaults against the BROWSER timezone, when there is no TimeZone specified. ==> It's just an offset, and does not bring DST in count. |
| Comments |
| Comment by Marta Kobus [ 30/Sep/21 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.
Thank you, The Magnolia Team |