Ensure only one flyout is open at a time #8069
-
|
Is your feature request related to a problem? Please describe. Here is an example in Kibana: elastic/kibana#193452 While things like this can be solved within a given solution, as seen here, it could be desirable to manage this more holistically, at a the EUI level. I'm not sure whether or not this is possible within EUI or not. If not, we may be able to implement a shared service via the Shared UX team. I think the first step would be to consider whether or not this is even possible in EUI and/or desirable in EUI. EUI flyouts currently have no awareness of one another. They have a simple show/hide toggle. There's no context of any sort that tracks what flyouts are already opened. We rely on consumers to track that state. The rules could get a bit tricky here, as well. For instance, it doesn’t make sense to allow multiple push flyouts, but a push and 1 overlay flyout could make sense, And additionally, I believe there were some proposals on the table at one point to allow multiple push flyouts at one time. Describe the solution you'd like Describe alternatives you've considered Desired timeline Additional context Related flyout issue: #7443 Another consideration: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
I've moved this to be a discussion. I'm not sure if this is something we want to adopt or not. This could be an EUI feature of a shared service in @elastic/appex-sharedux We'd need to determine the best approach here and what the rules would be. |
Beta Was this translation helpful? Give feedback.
-
|
@kertal With the addition of "session" flyouts in EUI, this should be resolved: #9068. I am going to close this discussion! |
Beta Was this translation helpful? Give feedback.
@kertal With the addition of "session" flyouts in EUI, this should be resolved: #9068. I am going to close this discussion!