Infinite loop if loadmore call results are empty and content not added in Chrome

[pavelg]

looks like the similar problem is in #186
bit now we have this only in Chrome browser

So, as soon as request finishes and we do nothing, the new loadMore event is triggered endlessly
UPD: it happens if scroll is fast, on scrolling down slowly it stops calling defaultHandler

Problem cause is Chrome's scroll anchoring
Temp fix is to apply overflow-anchor: none to parent container