Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[ClickAwayListener] Is being fired without an onClick event after upgrading react and react-dom to v17
See original GitHub issueOn my app I have a menu that worked fine until I upgraded react and react-dom.
After upgrading react and react-dom from version 16.14.0 to version 17.0.0- on menu click, the menu flashes-it opens and closes right away.
- The issue is present in the latest release.
- I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
On menu click- the menu opens and closes right away, for some reason the ClickAwayListener is being fired.
Expected Behavior 🤔
On menu click- the menu should open, on click away it should close.
Steps to Reproduce 🕹
Steps:
- Upgrade
reactandreact-domto v17.0.0 - Click the menu
Codesandbox: ~https://codesandbox.io/s/material-ui-issue-forked-byfgm?file=/src/index.js~ Invalid. New repro: https://codesandbox.io/s/material-ui-issue-forked-13053?file=/src/Demo.js
Your Environment 🌎
| Tech | Version |
|---|---|
| Material-UI/core | v4.11.0 |
| React | v17.0.0 |
| React-dom | v17.0.0 |
| Chrome | v86.0.4240.75 |
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:25 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
What about the use case where you have a
<Popper />and put a<ClickAwayListener />on thechildren?Sandbox for the issue @stevewillard stated. Using a popper with a clickaway listener in it.