-
-
Notifications
You must be signed in to change notification settings - Fork 983
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
fix close release destroyObserver #1229
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good spot, not sure what happened there. Interested to know how you spotted it. Was it causing an issue?
src/iframeResizer.js
Outdated
@@ -68,7 +68,8 @@ | |||
onScroll: function () { | |||
return true | |||
} | |||
}) | |||
}), | |||
destroyObserver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please move this up into the alphabetical order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
I found that in Chrome memory watcher, when I destroy the iframe element, this object still get reference to frame object as DetachIFrameObject |
Just tried to merge this but I get the following eslint errors
|
@aniude I think the first issue can be fixed by changing destroyObserver && destroyObserver.disconnect() to destroyObserver?.disconnect() Not sure what is causing the second warning |
I changed it. check it again. |
Merged into V4 branch and released as v4.3.10 Thanks for the fix. Btw you might want to checkout the version 5 I'm currently working. Draft docs can be found at http://iframe-resizer.com. Would love any feedback on it that you might have. |
It seems that the UI is more better. I can't wait anymore. thanks. |
No description provided.