[1.0.0] isLazy prop on Popover error when close
See original GitHub issueBug report
Using isLazy
prop on Popover
component, when close
Popper: “arrow” modifier’s
element
must be a child of the popper element.
To reproduce
- Click Trigger button
- Click outside
- Check console.log
- See error
Minimal reproduction
Reproduction https://codesandbox.io/s/snowy-silence-xftso?file=/src/App.js
Screenshots
System information
- Browser (if applies): [e.g. Chrome, Safari]
- Version of @chakra-ui/react: [e.g. 1.0.0]
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:8 (4 by maintainers)
Top Results From Across the Web
react-native-router-flux/CHANGELOG.md - UNPKG
17, - after update to Release 4.0.2 props not working. ... a function \(evaluating 'addListener'\) with the new stable release of react-navigation \(1.0.0\) ......
Read more >converse.js at [b24370a6e5] - Keyframe
@param {Array} props The property names to get values for. ... The execution of chained methods is lazy, that is, it's deferred until...
Read more >react-native-router-flux | Yarn - Package Manager
Actions.replace: There is no route defined for Key X #3258; after update to Release 4.0.2 props not working... #3206. Closed issues: Error on...
Read more >react-native-walkthrough-tooltip - npm
No more animated prop - if you want to have your tooltips animated, use the last stable version: 0.6.1 . Hopefully animations can...
Read more >Falcon Sandbox v8.31 © Hybrid Analysis
Screenshots. Data couldn't be loaded. Please try again. ×Close ... Reduced Monitoring, Network Activityy, Network Error, Multiscan Match ...
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
The issue out again in
1.1.5
This error doesn’t occur in the most recent version. Kindly upgrade