Time selector handles timezone improperly

[u74a8]

WHAT IS THE BUG

In Tasks set when “Include time” for “Due date” column is enabled, the time selector cannot handle timezone properly.

HOW TO REPRODUCE IT

1. Set your system timezone to UTC+X.
2. Open a Tasks set in Anytype, click on “Due date” column and enable “Include time”.
3. Click on the “Due date” relation for a task and type in a time value Y.
4. Click on some blank area or press Enter to confirm the edit.
5. The saved time value displays as Y-X.

THE EXPECTED BEHAVIOR

The time selector should handle timezone properly. When I type in Y, I mean Y but not Y-X.

SYSTEM INFORMATIONS

• OS:
  Windows 11 21H2
• Device:
  Lenovo Air 14
• Anytype Version:
  0.29.0

ADDITIONAL CONTEXT

Here’s a related bug report, but it only resoves displaying problem, not editing.

The time value for the "Creation date" relation is always in GMT, regardless of the system's time locale

Describe the bug When the “Creation date” relation is enabled with the “Include time” option toggled on, the time that is displayed is always in the GMT time zone, not in the system’s time zone. [image] To Reproduce Open a Set and toggle on the Relation for Creation Date Enable the “Include time” option Create a new Object within the Set and observe the time displayed in the Creation Date relation. The Object that is visible in the screenshot had just been created right before the screens…

[kerbless]

Other possibly relevant topics:

Sometimes picking a date selects the day before

Describe the bug Sometimes picking a date displays and selects the day before. To Reproduce Steps to reproduce the behavior: Open any date relation Select some dates (seems like the problem happens with older dates) Expected behavior The day typed/selected should be the one added and displayed to the property System Information: OS: Windows 10/11 Anytype Version: 0.27.0 Additional context Related to: A comprehensive anytype first impression

Date fields and Timezones

Describe the bug It seems the Creation date column in this image is using the wrong timezone or something to determine whether it’s “yesterday” or not… As you can see in the bottom right, it’s still the same day, Feb. 11, for me atm To Reproduce Any date field with a date on the same day will say “Yesterday” a few hours before the day has actually changed for me. It seems like this might be some timezone issue. My timezone is CST (America/Chicago). Expected behavior In the image provided, i…

plus the one already mentioned in the additional context.

[kerbless]

Hi @u74a8, do you still have this issue?

[u74a8]

Yes. In 0.29.1 this issue still exists.

[Angelo]

This issue has been fixed by the Development Team and will be implemented in an upcoming release.