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 Apr 15, 2019. It is now read-only.
Hi,
One "good practice" in angularjs is not to keep DOM elements in the scope.
This might result in memory leaks.
When I'm doing this: <div kendo-grid="grid"></div>
I'm actually getting the object grid in my scope, and in turn, grid.element, which references to a DOM element.
Am I right in this? Can this be a reason for memory leaks? If so, how can one avoid it and what would be the best practice in releasing the DOM element? Or maybe you take care of it in the directive itself?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
One "good practice" in angularjs is not to keep DOM elements in the scope.
This might result in memory leaks.
When I'm doing this:
<div kendo-grid="grid"></div>
I'm actually getting the object
grid
in my scope, and in turn,grid.element
, which references to a DOM element.Am I right in this? Can this be a reason for memory leaks? If so, how can one avoid it and what would be the best practice in releasing the DOM element? Or maybe you take care of it in the directive itself?
The text was updated successfully, but these errors were encountered: