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
Please provide the environment you discovered this bug in.
<ngx-sonner-toastercloseButton="true"/>
toast.error('Error toast',{dismissable: false});
Description
When the closeButton option is set to true, all of my toasts have a close button. However, if I launch a toast with dismissable: false, the close button is still enabled and functional. Is this behavior intentional? How can I disable the closing of an individual toast if I have closeButton: true? It should at least work like the behavior of toast.loading()."
Please provide the exception or error you saw
No response
Other information
No response
I would be willing to submit a PR to fix this issue
Yes
No
The text was updated successfully, but these errors were encountered:
Please provide the environment you discovered this bug in.
Description
When the closeButton option is set to true, all of my toasts have a close button. However, if I launch a toast with dismissable: false, the close button is still enabled and functional. Is this behavior intentional? How can I disable the closing of an individual toast if I have closeButton: true? It should at least work like the behavior of toast.loading()."
Please provide the exception or error you saw
No response
Other information
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: