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 could be done by putting start time into localStorage when a timer is started, and deleting it when stopped, so that when the page is first loaded, if any tasks/times exist in localStorage, we know that that's an actively running timer, and should preset it with the correct amount of time and start it.
The text was updated successfully, but these errors were encountered:
This has been started in the feature/persistenttimers branch. It saves entries with running timers persistently, but getting them to start back up again on page load with the correct amount of time isn't super simple since that's not how the timers were built to work, so I'm temporarily halting work on this until I can find out if more people are interested in it.
I think it's valuable to restore it as a completed time entry, message indicating it had been in progress for extra sauce. That way if you start the timer but close the browser without saving you don't entirely lose what you were doing.
I'm hoping that the "close your browser and lose everything" thing won't happen much in practice since you'll have to confirm this popup in the process, but I still see your point, and restoring it as completed would be a bit easier than continuing the timer as if it had never stopped.
This could be done by putting start time into localStorage when a timer is started, and deleting it when stopped, so that when the page is first loaded, if any tasks/times exist in localStorage, we know that that's an actively running timer, and should preset it with the correct amount of time and start it.
The text was updated successfully, but these errors were encountered: