Page MenuHomePhabricator

Make calendar intepret all-day dates in a more consistent way
ClosedPublic

Authored by epriestley on Oct 31 2016, 6:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 11, 7:38 AM
Unknown Object (File)
Thu, Apr 11, 4:12 AM
Unknown Object (File)
Mon, Apr 8, 8:40 AM
Unknown Object (File)
Tue, Apr 2, 3:19 AM
Unknown Object (File)
Fri, Mar 29, 8:12 PM
Unknown Object (File)
Feb 12 2024, 5:38 PM
Unknown Object (File)
Feb 12 2024, 3:26 PM
Unknown Object (File)
Feb 6 2024, 1:57 AM
Subscribers
None

Details

Summary

In ICS, an event on "Nov 1" starts on "2016-11-01" and ends on "2016-11-02".

This is convenient for computers, but this isn't what users expect to enter in date controls. They expect to enter "nov 1" to "Nov 1" for a one-day, all-day event. This is consistent with other applications.

Store the value the user entered, but treat it as the first second of the next day when actually using it if the event is an all day event.

Test Plan

Mucked around with multi-day all-day events, recurring all-day events, imports, etc. Couldn't catch any weird/unintuitive stuff anymore offhand.

(Previously, entering "Nov 1" to "Nov 2" created a one-day event, which was unclear.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make calendar intepret all-day dates in a more consistent way.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Oct 31 2016, 7:05 PM
This revision was automatically updated to reflect the committed changes.