Open SaintFlipper opened 9 years ago
yea, looks like a bug. it similar to the problem with the inline elements. We have a problem with the setup when elements can jump rows as the width changes. I will mark it as a bug and we will try to fix it, in the meantime a possible solution would be to place everything going into a single row in a separate div.
On the side note we moved the code to angular-ui. All further development will be done in the angular-ui repo
An issue was created in angular-ui repo: https://github.com/angular-ui/ui-scroll/issues/8.
@SaintFlipper I am not sure if this notification made it to you. I think we have a fix for the problem you reported here, but this fix is in the new repo. In general going forward all new development, including fixes will be in the new repo
Hi, this is the secondary issue raised as a side-effect in #89 ("No way to limit the data source top"). I've opened a new issue as it's really a different artifact and not related to negative indices.
If NGScroller is used to handling scrolling of multiple items per line its behaviour is confused when the user tries to scroll upwards:
Standalone example at: http://jsfiddle.net/mn59dvjn/5/ Note: make the jsFiddle result pane wide enough to display at least 4 images per row to see the above effects.