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
Do you want to request a feature or report a bug?
Report a bug
What is the current behavior?
When manually setting progress to 1 via toast.update(toastId, { progress: 1 }), the toast auto closes even when autoClose: false is set.
Steps to Reproduce + Repro:
Create a toast that should not auto close using const toastId = toast('your message', { autoClose: false })
update the toast's progress manually using toast.update(toastId, { progress: 1 })
What is the expected behavior?
If I use autoClose: false, then the toast should not close automatically
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
React 18, chromium based browser on Mac. I'm uncertain how this behaves on old versions of React
The text was updated successfully, but these errors were encountered:
@shamoilarsi this still does not give the desired behavior. The suggestion in that code will remove the progress bar completely, which I don’t want, I want to see a completed progress bar.
Do you want to request a feature or report a bug?
Report a bug
What is the current behavior?
When manually setting
progress
to 1 viatoast.update(toastId, { progress: 1 })
, the toast auto closes even whenautoClose: false
is set.Steps to Reproduce + Repro:
const toastId = toast('your message', { autoClose: false })
toast.update(toastId, { progress: 1 })
CodeSandbox: https://codesandbox.io/p/sandbox/react-toastify-autoclose-with-progress-n5d5jg
What is the expected behavior?
If I use
autoClose: false
, then the toast should not close automaticallyWhich versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
React 18, chromium based browser on Mac. I'm uncertain how this behaves on old versions of React
The text was updated successfully, but these errors were encountered: