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
I would strongly encourage to trigger all DOM events outside the zone in order to get additional performance out of gridster2.
I am currently implementing gridster2 into existing project, where each GridItem contains one pretty expensive component, and I can totally feel the problem.
Another scenario where this can cause problems are applications in migration from AngularJS to Angular by using ngUpgrade, since there $digest is triggered in addition.
On your demo app
Inside angular
Outside angular
The text was updated successfully, but these errors were encountered:
I would strongly encourage to trigger all DOM events outside the zone in order to get additional performance out of gridster2.
I am currently implementing gridster2 into existing project, where each
GridItem
contains one pretty expensive component, and I can totally feel the problem.Another scenario where this can cause problems are applications in migration from AngularJS to Angular by using ngUpgrade, since there
$digest
is triggered in addition.On your demo app
Inside angular
Outside angular
The text was updated successfully, but these errors were encountered: