fix: clear stale timer state on new workout start#31
Merged
Conversation
When navigating away from a workout while a rest timer was running (e.g. pressing Back), the timer state was left in IndexedDB. On the next workout load, the recovery code would find the stale timer and fire the notification and/or show "Time's Up!" immediately. Two fixes: 1. renderWorkout now clears any stale timer state when starting fresh (not resuming an active workout), preventing the recovery code from misinterpreting a leftover timer from a previous session. 2. The Back button handler now calls putTimerState(null) so the timer is explicitly cleaned up when the user navigates away mid-rest. https://claude.ai/code/session_01W41HrMh4pZma1AiT7fHRxd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.