Please check this jsFiddle. (The code is basically the same you posted but I use an element instead of the window to bind the scroll events).
As far as I can see, there is no problem with the code you posted. The error you mentioned normally occurs when you create a loop of changes over a property. For example, like when you watch for changes on a certain property and then change the value of that property on the listener:
$scope.$watch('users', function(value) {
$scope.users = [];
});
This will result on an error message:
Uncaught Error: 10 $digest() iterations reached. Aborting!
Watchers
fired in the last 5 iterations: …
Make sure that your code doesn’t have this kind of situations.
update:
This is your problem:
<div ng-init="user.score=user.id+1">
You shouldn’t change objects/models during the render or otherwise, it will force a new render (and consequently a loop, which causes the ‘Error: 10 $digest() iterations reached. Aborting!’).
If you want to update the model, do it on the Controller or on a Directive, never on the view. angularjs documentation recommends not to use the ng-init exactly to avoid these kinds of situations:
Use ngInit directive in templates (for toy/example apps only, not
recommended for real applications)
Here’s a jsFiddle with a working example.