Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snackbars stop showing after few clicks #270

Closed
nebojsanb opened this issue May 16, 2020 · 3 comments
Closed

Snackbars stop showing after few clicks #270

nebojsanb opened this issue May 16, 2020 · 3 comments

Comments

@nebojsanb
Copy link

nebojsanb commented May 16, 2020

Great tool first of all. Thank you for sharing it.

I am testing some login logic and I generated few (~4) Snackbars in a few seconds. I noticed that after that, they stopped showing up altogether.

Expected Behavior

I believe that they should show up all the time unless configured differently.

Current Behavior

After a few clicks, they stop appearing. I also noticed that after the third one (in most of the cases but not always) the fourth one is shown with a few sec delay. After that, no more Snackbars are shown on the screen. In my app maxSnack={3}.

Steps to Reproduce

In codesandbox.io I had to click more times comparing to my app, but eventually (maybe 10-15 times) it also stopped working.

Link:
https://codesandbox.io/embed/eager-einstein-1rno0?fontsize=14&hidenavigation=1&theme=dark

Your Environment

"react-dom": "^16.13.1"
"@material-ui/core": "^4.9.14"
"notistack": "^0.9.14"
Browser: Version 81.0.4044.138 (Official Build) (64-bit)

@hippotastic
Copy link

I have the same issue. This is new with 0.9.14. If I downgrade to 0.9.13, everything starts working again.

iamhosseindhv added a commit that referenced this issue May 17, 2020
@iamhosseindhv
Copy link
Owner

iamhosseindhv commented May 17, 2020

Thanks for reporting this guys.

This bug was introduced by material-ui's latest changes (about a week ago) in handling react-transition-group callbacks.
mui/material-ui#21091

Recent changes in v0.9.14 made the bug visible to the end users. Anyhow, it is fixed and going to be published in a few hours.

@xuxusheng
Copy link

the same to me,it took me hours to check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants