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
Every page click will throw a CLOSE_Q_SEARCH timed out-error.
This is because BaseExperienceFrame adds a mutation observer on the body element, but this mutation observer only checks for node === this.iframe || node === this.container.
Because of this, if the parent element of the container element (or any of its parents) get removed from the DOM, no cleanUpCallbacks actually execute.
This feels like unexpected behaviour as there are leaky object references & event listeners that stay active even after the embedded Quicksight element is destroyed.
The text was updated successfully, but these errors were encountered:
Potentially, we could use document.body.contains(node) instead of checking for equality on a removed node, but I'm not sure about possible performance implications here (since we're traversing the DOM on every mutation).
Steps to reproduce
QSearchBar
url hereResult
Every page click will throw a
CLOSE_Q_SEARCH timed out
-error.This is because
BaseExperienceFrame
adds a mutation observer on the body element, but this mutation observer only checks fornode === this.iframe || node === this.container
.Because of this, if the parent element of the
container
element (or any of its parents) get removed from the DOM, nocleanUpCallbacks
actually execute.This feels like unexpected behaviour as there are leaky object references & event listeners that stay active even after the embedded Quicksight element is destroyed.
The text was updated successfully, but these errors were encountered: