You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feels counter-intuitive and at the very least should be exposed on the filter form, and ideally should not match by default in these cases. As a more visual example, take the following:
Currently, choosing "2049/10/05" as the start date to filter will still include every date before it, e.g. "2049/10/04", "2049/10/03", etc., which doesn't make intuitive sense. The same goes for the end date. What is expected from a user's point of view is that choosing an explicit date will exclude all dates outside of that range. For example, choosing "2049/10/05" as a start date should not match "2049/10/04", "2049/10/03", etc.
This feels counter-intuitive and at the very least should be exposed on the filter form, and ideally should not match by default in these cases. As a more visual example, take the following:
Currently, choosing "2049/10/05" as the start date to filter will still include every date before it, e.g. "2049/10/04", "2049/10/03", etc., which doesn't make intuitive sense. The same goes for the end date. What is expected from a user's point of view is that choosing an explicit date will exclude all dates outside of that range. For example, choosing "2049/10/05" as a start date should not match "2049/10/04", "2049/10/03", etc.
See neurocracy/drupal-omnipedia-date#2 for implementation details.
The text was updated successfully, but these errors were encountered: