You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Looker Embed exposes a drillmodal:click and dashboard:schedule_modal:open events.
I am currently working on an Embedded Application which has a need to track the open/closed state of Looker Embed modals, in order to update certain components of our host application's UI. Currently, while it is possible to track modal open events in certain cases, there is no corresponding modal:close event which we might use to track the open/closed state.
It would be very helpful if the Embed could expose a single modal:open and corresponding modal:close event to allow for this kind of fine-grained UI integration.
I understand this would not be a feature unique to the Embed SDK, and that it would in fact need to exist within the Embed iframe's application logic itself, but I wasn't sure where to create this feature request if not in this repository. Happy to move this request to wherever it makes the most sense if someone doesn't mind letting me know how to go about that!
The text was updated successfully, but these errors were encountered:
Currently, the Looker Embed exposes a
drillmodal:click
anddashboard:schedule_modal:open
events.I am currently working on an Embedded Application which has a need to track the open/closed state of Looker Embed modals, in order to update certain components of our host application's UI. Currently, while it is possible to track modal open events in certain cases, there is no corresponding
modal:close
event which we might use to track the open/closed state.It would be very helpful if the Embed could expose a single
modal:open
and correspondingmodal:close
event to allow for this kind of fine-grained UI integration.I understand this would not be a feature unique to the Embed SDK, and that it would in fact need to exist within the Embed iframe's application logic itself, but I wasn't sure where to create this feature request if not in this repository. Happy to move this request to wherever it makes the most sense if someone doesn't mind letting me know how to go about that!
The text was updated successfully, but these errors were encountered: