Mount node on Portal components crashes when specified node inside the current component
See original GitHub issueIn the sandbox https://codesandbox.io/s/ly54m63vz7, there is a reproduction case and a hack to fix if encountered.
The clean fix would be to use a function getMountNode
instead of as well as mountNode
for these use cases. Note that this API is used (getPopupContainer) in https://github.com/react-component/trigger and in Ant Design components
Steps
Set mountNode
of a Portal component to its parent
Expected Result
the portal should mount on the specified mountNode
Actual Result
Crashes Cannot read property 'appendChild' of null
Version
0.75.1
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
RHSA-2022:5069 - Security Advisory
prometheus/client_golang: Denial of service using InstrumentHandlerCounter (CVE-2022-21698); golang: crash in a golang.org/x/crypto/ssh server ( ...
Read more >Node.JS: Getting error : [nodemon] Internal watch failed
It appears that my max ports weren't configured correctly. I ran the following code and it worked... echo fs.inotify.max_user_watches=582222 | sudo tee -a ......
Read more >Let It Crash: Best Practices for Handling Node.js Errors on ...
It's simpler to let it crash, start a new process from scratch, and continue receiving more requests. We're explicitly “crashing” the Node. js ......
Read more >Frequently asked questions for Azure Kubernetes Service ...
Change the node resource group name after the cluster has been created. Specify names for the managed resources within the node resource group....
Read more >How to solve "window is not defined" errors in React and ...
Because in the Node.js world, window is not defined, window is only ... load a component and forget about it (no more mount/unmount...
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 Free
Top 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
I’m almost sure that we don’t need to fix this as it’s an edge case. Possible @levithomason has another opinion.
it turns out I just needed to upgrade semantic-ui-react to 0.84