Autoclose not working if progressbar hidden via display non
See original GitHub issueDo you want to request a feature or report a bug? Bug
What is the current behavior?
Toast not autocloses if progress bar is hidden via display: none
.
Hiding it by default method (opacity) is not working because of IE11 flexbug (https://github.com/philipwalton/flexbugs/issues/111).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to set up an independent progress bar - Stack Overflow
Is there a way to implement an bar that progresses on top of a calculation, independently and continuously, for a fixed amount of...
Read more >Use progress bar from python - 3D Slicer Community
I would like to add a progress bar in the UI. Is there any way to work with a progressbar info from python?...
Read more >QProgressDialog — Qt for Python - Qt Documentation
Resets the progress dialog. The progress dialog becomes hidden if autoClose() is true. This property holds whether the dialog gets hidden by reset()...
Read more >How to style | React-Toastify - GitHub Pages
#Override existing css classes. If overriding the css variables is not enough for you, you can override the existing CSS classes. Below, a...
Read more >User and Workspace Settings - Visual Studio Code
As an example, let's hide the Activity Bar from VS Code. The Activity Bar is the ... If you prefer to always work...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI I am solving the problem without importing CSS by using TypeStyle, although any CSS injection tool will do:
I must agree, an element that must be rendered in the page that we can easily remove using css affecting the behavior of the toast is wild. I was scratching my head as to what was going on.
Please document this somewhere in the autoClose section: https://fkhadra.github.io/react-toastify/autoClose