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
We're using ngTemplates Grunt plugin to check get all the templates and put them into $templateCache service.
Please note that all the template are included, the paths are correct within this service, everything works ok either by removing the ngProgress.color('#66afda'); line, or commenting out the line where the scope is manually applied (from ngProgress code).
The text was updated successfully, but these errors were encountered:
Getting the same issue in pretty much the same conditions.
I've traced the cause to inside the color method, to the $scope.$$phase and $scope.$apply calls. But after working on it for a good amount of time, we decided to just !important the background-color from CSS.
Here's a sample of
run()
methodand here's a sample of routes configuration
We're using ngTemplates Grunt plugin to check get all the templates and put them into $templateCache service.
Please note that all the template are included, the paths are correct within this service, everything works ok either by removing the
ngProgress.color('#66afda');
line, or commenting out the line where the scope is manually applied (from ngProgress code).The text was updated successfully, but these errors were encountered: