react-toast component does not seem to resume timer once a toast was actioned (and closed) via action or close button, which causes all subsequent toasts to be permanently stuck on a screen.
I've made a codesandbox that console logs using onPause and onResume methods to better illustrate the issue.
In the video above I first trigger a toast and hover/unhover it to illustrate how timer is paused and resumed and then let it auto dismiss when it exceed the timer limit (unrelated to a bug reproduction itself, purely to show pause/resume messages)
Then I click "undo" button that triggers "pause" and never resumes, from that moment on all subsequent toasters will be permanently stuck until you manually close them.
Focusing on other elements does not help either.
Expected behaviour
Clicking toaster action/close buttons should resume the counter, so toasters in future does not start with paused state.
Bug report
react-toast component does not seem to resume timer once a toast was actioned (and closed) via action or close button, which causes all subsequent toasts to be permanently stuck on a screen.
I've made a codesandbox that console logs using onPause and onResume methods to better illustrate the issue.
Current Behaviour
Kapture 2023-07-12 at 09.54.42.webm
In the video above I first trigger a toast and hover/unhover it to illustrate how timer is paused and resumed and then let it auto dismiss when it exceed the timer limit (unrelated to a bug reproduction itself, purely to show pause/resume messages)
Then I click "undo" button that triggers "pause" and never resumes, from that moment on all subsequent toasters will be permanently stuck until you manually close them.
Focusing on other elements does not help either.
Expected behaviour
Clicking toaster action/close buttons should resume the counter, so toasters in future does not start with paused state.
Reproducible example
CodeSandbox Template