Sometimes we implement a feature in the simplest way that works. It does the job, you can use it, and we move on. But “works” from a development point of view does not always mean it behaves quite as a user would expect.

Calendar navigation was one of those things. It worked, provided you gave it a moment between clicks. A small detail we had rather optimistically left to your patience. Hands up: we should have handled it better.

Every click should count

If you want to move forward three months, clicking the forward button three times is a perfectly reasonable thing to do. You should not have to wait for the calendar to finish loading between clicks.

Previously, clicks made close together could work from the same starting point while an earlier update was still being processed. You could click three times and find that the calendar had moved less than you expected.

The calendar now keeps track of your actions and applies them in the order you made them. Click forward three times and it moves forward three steps. Move forward, then back, and those actions are handled in that order too. Changes to the date range and other calendar controls follow the same approach.

Keeping the view consistent

There is more to this than moving the dates. The calendar on screen, the view remembered for your next visit, and browser navigation all need to agree. An older update finishing late should not pull you away from a view you have returned to with the Back button.

We have tightened up how those updates fit together. If a calendar update fails, a message tells you that your changes are waiting, with a Retry changes button to try again.

There is no new feature to learn here. The calendar controls should have behaved this way all along. If you have had to click again or wait between clicks to get where you wanted, sorry for the frustration. Keeping count is a fairly reasonable thing to ask of accounting software!