- Time format for Firefox is -1 minute
- The actual data is still correct (that is, 11:59 AM internally is still 12:00 PM, for instance), so it's at least ignorable: visual bug only.
- Returning to a page when an active timer was left running but has expired since you left will leave the timer in an inconsistent state: 0s left but still "running"
- Some times (some scenarios) will cause the timer to not start actively counting down on the page
- Some scenarios will cause a bunch of notifications to be sent all at once
- I suspect this is related to the subscriber being updated that the countdown is complete but not being unsubscribed
- Seems to have fixed itself through one refactor or another
- The "On Deck" label does not correctly update if you edit the label of the on-deck timer
- Editing timers while one is running has not yet been tested
- Edits to min/max values are sometimes erased / not saved
- Deleting the current ticountdown will cause a crash
- Timers not rolling over when completed (e.g. work completes, break is not queued up to be on deck)
- Notifications broke on Firefox for some reason
- This is due to a bad configuration on my computer