Popover "enabled" prop not working
See original GitHub issueDescription
When “enabled” is set to false on a Popover… it should be disabled
Link to Reproduction
https://codesandbox.io/s/compassionate-hawking-l41nb
Steps to reproduce
- Click on popover
- It should not open but opens
Chakra UI Version
1.7.2
Browser
Firefox
Operating System
- macOS
- Windows
- Linux
Additional Information
I think that the enabled
prop gets overwritten here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Material UI popover not working with react class component
I can not figure out why the popover is not working. Whenever I hover over the text the function is triggered but popover...
Read more >Overlays | React-Bootstrap
The <Tooltip> and <Popover> components do not position themselves. Instead the <Overlay> (or <OverlayTrigger> ) components, inject ref and style props.
Read more >React-native-popover-view - npm.io
A well-tested, adaptable, lightweight <Popover> component for react-native with no dependencies. Tested and working on iOS and Android. May work on Web, but...
Read more >react tiny popover not working - pravdabl.com
I'm attempting to create a popover and the popover example provided by react-bootstrap docs is not working. <Controller> will hold the part of...
Read more >Accessibility - React
Also note the added aria-* props to support screen-reader users. For simplicity's sake the keyboard events to enable arrow key interaction of the...
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 FreeTop 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
Top GitHub Comments
FYI as a workaround I’m using:
to disable popover when
isEnabled === false
The
enabled
prop wasn’t intended to be exposed to the user-land. It was a side-effect of extending theUsePopperProps
and I’ve gone ahead to omit it from types.