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 May 29, 2019. It is now read-only.
Whenever a tooltip is shown, any old tooltip element is destroyed and a new one is created. Since the tooltip element contains a tooltipPopup that creates a new scope, each show/hide of a tooltip creates a new scope that remains until the parent scope is destroyed.
To reproduce:
Use something like Batarang to observe the scope hierarchy
Move your mouse back and forth across an element with a tooltip
Watch the list of scopes continue to grow
Adding tooltip.children().scope().$destroy() right before tooltip.remove() in removeTooltip() seems to fix the issue.
The text was updated successfully, but these errors were encountered:
I tried to set up a plunker to demo the bug, but dev tools don't seem to see the frame the stuff is in, so here is a static html page you can just load to see the issue. Reproduced on Chrome in Win7.
Create a new child scope and retain a reference to it so that it can
be destroyed when the tooltip DOM is removed.
Fixesangular-ui#2709Closesangular-ui#2919
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Whenever a tooltip is shown, any old tooltip element is destroyed and a new one is created. Since the tooltip element contains a tooltipPopup that creates a new scope, each show/hide of a tooltip creates a new scope that remains until the parent scope is destroyed.
To reproduce:
Adding
tooltip.children().scope().$destroy()
right beforetooltip.remove()
inremoveTooltip()
seems to fix the issue.The text was updated successfully, but these errors were encountered: