[MGNLUI-5817] DateField time zone issue Created: 14/Apr/20  Updated: 28/Jul/21  Resolved: 16/Apr/20

Status: Closed
Project: Magnolia UI
Component/s: forms
Affects Version/s: 6.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: fields
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File user-timezone.png    
Issue Links:
Relates
relation
is related to MGNLUI-6164 Scheduled publication date is shown w... Closed
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
Epic Link: Dialog UX improvements

 Description   

There seems to be an issue with the DateField and time zones.

To see the issue:

  • Go to the demo.
  • Publish and schedule a page for 2 minutes later.
  • Assign and approve it.
  • Wait until the time arrives and notice the page does not publish.

Even if I try to set my user profile it has no effect on the field.

Since Vaadin 8 AbstractDateField has a #setZoneId() method.

If the author instance is in one time zone, and the user is in another, how should that be handled when trying to schedule publication so that the user does not need to calculate a time. It might even be a good idea to have a confirmation on the publish button to reaffirm the time is understood.



 Comments   
Comment by Richard Gange [ 16/Apr/20 ]

After some investigation I realize now the problem is not with the date field. It's the dialog for the user settings. It's not writing the timezone property in the wrong format for the date field. If I manually add the property with a short code value the scheduled task runs correctly.

Generated at Mon Feb 12 09:30:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.