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
{{ message }}
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.
Some globals are ok, such as IntersectionObserver, etc. But many could be harmful for components running inside friendly iframes. For instance window.location.href could be different from component.baseElement.ownerDocument.defaultView.location.href. Some specific points:
A component running inside a friendly iframe could have a completely different baseURI and thus could be resolving URLs incorrectly.
Use of global setTimeout, setInterval, and event listeners (e.g. window.onresize) could cause memory leaks when a friendly iframe is removed.
Rare, but if a component needs to call document.querySelector() and would do it on a wrong document, it won't find what's it looking for.
The text was updated successfully, but these errors were encountered:
Some globals are ok, such as
IntersectionObserver
, etc. But many could be harmful for components running inside friendly iframes. For instancewindow.location.href
could be different fromcomponent.baseElement.ownerDocument.defaultView.location.href
. Some specific points:baseURI
and thus could be resolving URLs incorrectly.setTimeout
,setInterval
, and event listeners (e.g.window.onresize
) could cause memory leaks when a friendly iframe is removed.document.querySelector()
and would do it on a wrong document, it won't find what's it looking for.The text was updated successfully, but these errors were encountered: