search

jankuca / ng-scroller

http://ngscroller.herokuapp.com
187 stars 27 forks source link

When scrolling quickly in up direction, See only white space #2

Open btesser opened 11 years ago

btesser commented 11 years ago

Mac OS X 10.8.4 Google Chrome 28.0.1500.95

When using "fling" type scrolling, or scrolling very quickly, it is easy to "confuse" the scroller. This begins to happen especially when scrolling back up a page. You end up in a situation where when scrolling down, just as you start to see posts appear, they disappear. It almost looks as though the directive thinks I am in a different position than I actually am. Sometimes all you see is 2 scrollbars. screen shot 2013-08-18 at 1 03 24 am screen shot 2013-08-18 at 1 03 17 am

jankuca commented 11 years ago

Thank you for your feedback.

I know about this issue and it is exactly as you think, there is a bug in the skew value which should track how much of the content is overflowing at the top. The popping and shifting behavior is controlled based on this value.

About the two scrollbar part… The large one is for the whole page while the smaller one belongs to the widget. There is really no native solution to this. Facebook for instance creates and manipulates its own scrollbar for the widget.

JohnMunsch commented 10 years ago

Having seen this problem and knowing that we really really need this library to be functional I've been looking for solutions. I noticed another library recently which is specifically designed to abstract away from hooking directly to the scroll event (which can be very problematic): https://github.com/pazguille/scrolling

It tries to filter out the huge number of scroll events which might be overwhelming your code and causing the glitches we are seeing.

kristianmandrup commented 10 years ago

I recommend that you have a look at BaconJS and Functional Reactive Programming in general. I'm pretty sure it would solve a lot of your problems in an elegant fashion, using EventStreams and Properties instead of a callback hell with too many evens, various timers etc. quickly making it all ay too complex to find decent solutions with all the state handing etc. Time to move on... ;)

https://github.com/baconjs/bacon.js

http://www.youtube.com/watch?v=jIsxcXBWthI

http://www.youtube.com/watch?v=nket0K1RXU4

eaoliver commented 10 years ago

Any plan to fix this? The library is mostly pretty nice, but too buggy to actually use.

akarelas commented 10 years ago

Maybe you guys want to check out https://github.com/Hill30/NGScroller (a similar project) while this bug is getting fixed.

bcherny commented 10 years ago

+1