Do you want to request a feature or report a bug?
feature
What is the current behavior?
The current behavior of the react-toastify library does not include a closeOnClickAway feature. This means that users cannot dismiss a toast by clicking outside of it. Recently, while browsing the documentation, I discovered this absence. This realization was echoed by a colleague who also inquired about the availability of this feature. Realizing its potential utility, I decided to take the initiative and work on adding the closeOnClickAway functionality to the library.
I would like to contribute by adding this functionality to the react-toastify library.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your CodeSandbox (https://codesandbox.io/s/new) example below:
What is the expected behavior?
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
Do you want to request a feature or report a bug? feature
What is the current behavior? The current behavior of the react-toastify library does not include a closeOnClickAway feature. This means that users cannot dismiss a toast by clicking outside of it. Recently, while browsing the documentation, I discovered this absence. This realization was echoed by a colleague who also inquired about the availability of this feature. Realizing its potential utility, I decided to take the initiative and work on adding the closeOnClickAway functionality to the library.
I would like to contribute by adding this functionality to the react-toastify library.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your CodeSandbox (https://codesandbox.io/s/new) example below:
What is the expected behavior?
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?