-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] Nested popovers #466
Comments
I've been looking into possible fixes for this and identified two approaches. Would love to hear your thoughts.
In other words, if the click comes from a nested element of the The |
Hi, This is really tricky to make it work across browsers. Removing document.body.click() will leave other popovers opened, so it's not an option, or at least not in this form. I think the solution is around your second approach, but got to ponder on this very good. Unfortunately, this won't happen so soon as the workload is huge at the moment. |
Hi,
|
Is it possible to register a callback with the popover so that before a popover is closed it calls this callback. If the callback doesn't exist or it returns true then allow the popover to close. Otherwise leave it open. Then the user can control which popovers stay open based on this custom callback that gets registered. |
I'm assuming this is still an issue? I noticed that the popovers had ref tags,however they don't seem to allow anything other than the individual items within them to control them... Doesn't stop the parent from closing when the child is opened. |
Nested Popovers are not supported. Can't accommodate all its features with this, and still make it work for the buggy webview in iOS platform. Sorry for any inconvenience. |
Currently it is not possible to create nested popovers like nested menus. Problem is then clicked on the second level popover button, the first level popover disappeared. It would be better to have, for example, property for popover to stay visible after clicking on another popover.
The text was updated successfully, but these errors were encountered: