[Snackbar] componenent message vanishes on mobile Firefox
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Current behavior 😯
Occasionally (can't figure out what variable causes it yet) on mobile, the snackbar message and actions vanish. They show up for a second on the snackbar, then then message and actions disappear, leaving just an empty (but still visible snackbar). The snackbar then vanishes soon after, respecting the autoclose time.
This is happening in Mobile Firefox, and I have not been able to replicate it on Mobile Chrome.
Any idea what might be causing this?
edit: Interestingly, when it gets into this state (snackbar showing but message not there), scrolling the window any amount will cause the message to appear again.
Expected behavior 🤔
Snackbar message and actions should be visible
Steps to reproduce 🕹
Can't reproduce, as it's only happening intermittently on mobile. It works fine on desktop, and I'm not using any breakpoints or conditional logic that would trigger only on mobile.
Context 🔦
No response
Your environment 🌎
npx @mui/envinfo
mui version = 5.8.3
(envinfo wasn't working:
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@mui%2fenvinf - Not found
npm ERR! 404
npm ERR! 404 '@mui/envinf@latest' is not in this registry.
npm ERR! 404
)
Mobile browser = Firefox
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Snackbar component in Material UI 5.8.3 and reproduce the intermittent failure on mobile Firefox, comparing it with mobile Chrome. Check whether scrolling restores the message and actions; done means they remain visible for the snackbar lifetime before autoclose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100