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
With the infiniteScroll fetaure, when the grid is loading additional data (i.e. page) while a menu or column menu is open, it will throw a [$rootScope:inprog] $digest already in progress exception.
Cause
This bug was introduced in v4.2.0 by this commit which replaces $timeout with $scope.$apply in many places for performance reasons.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. If you believe that this is still an issue in the latest version, feel free to re-open it. Thank you for your contributions.
Hi,
Any news about this please ?
The problem still exists. Replace $scope.$apply by $timeout in applyHideMenu doesn't seems to fix that. In fact, doing this, the menu open and close instantly...
Bug Description
With the infiniteScroll fetaure, when the grid is loading additional data (i.e. page) while a menu or column menu is open, it will throw a
[$rootScope:inprog] $digest already in progress
exception.Cause
This bug was introduced in v4.2.0 by this commit which replaces
$timeout
with$scope.$apply
in many places for performance reasons.Specifically,
dataLoaded
- which is what users call once additional data has finished loading - callsadjustScroll
which calls$rootScope.$applyAsync
and indirectly wraps abeginScroll
event trigger which has a registered handler in the column menu which in turn calls$scope.$apply
again inapplyHideMenu
.Possible Fix
$timeout
inapplyHideMenu
in place of$scope.$apply
, or:$apply
wherever we use$scope.$apply
/$scope.$applyAsync
The text was updated successfully, but these errors were encountered: