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
They appear to determine the timestamp at the current center of the date axis, and then center the day/month/year around that timestamp. That's really confusing when, say, zoomed into a week--especially a recent week--and then you click "year". You end up with ~6 months of future (see issue #10), which is of course empty.
Anyway, I'd love to see functionality driven by user testing feedback. For me at least, I always expect the buttons to give me the most recent day/month/year and am always surprised that they don't 🤷♂️
The text was updated successfully, but these errors were encountered:
My thinking was that by the principle of least surprise, they should not cause a jump that causes me to lose track of where I was in the timeline, as we have no good way of going back to where we were before clicking the button.
The >> button is the one in that group that does this jump explicitly, and it being right next to the day/month/year buttons, it seems like having to do a 2nd click for gong to "the current year" is the lesser evil.
They appear to determine the timestamp at the current center of the date axis, and then center the day/month/year around that timestamp. That's really confusing when, say, zoomed into a week--especially a recent week--and then you click "year". You end up with ~6 months of future (see issue #10), which is of course empty.
Anyway, I'd love to see functionality driven by user testing feedback. For me at least, I always expect the buttons to give me the most recent day/month/year and am always surprised that they don't 🤷♂️
The text was updated successfully, but these errors were encountered: