Ngx-infinite-scroll: ScrollUp does not fire or fires repeatedly

Created on 2 May 2018  路  6Comments  路  Source: orizens/ngx-infinite-scroll


Your issue may already be reported!
Please search on the issue track before creating one.

Expected Behavior

Scroll up should fire when the top percentage of the container is reached and should only fire once.

Actual Behavior

Scroll up is only firing if the percentage is set to 60% or above. Additionally when it does fire it triggers a cascading event that ends up firing until the API quits returning data.

Possible Solution


Steps To Reproduce / Demo (if applicable)

In progress

Context

Working to load previously read messages in response to the user scrolling up a list built using a ul and *ngFor.

Your Environment

Google Chrome Version 65.0.3325.181 (Official Build) (64-bit)

question

Most helpful comment

+1!

All 6 comments

Also having this issue. Has anybody found a solution?

+1!

I also wonder if it could have something to do with throttling not working.

for scroll up to work, the container needs to have the scroll set to be at the bottom OR after the "distanceUp" point.

Could you expand upon your answer a little more? I'm not quite clear what I would need to change

I'm using this for my container:

/* Scroll-contents, but start at bottom of container */
.scroll-contents-bottom {
flex-grow: 1;
overflow: auto;
display: flex;
flex-direction: column-reverse;
}

and tried using the default infiniteScrollUpDistance of 1.5, but it won't trigger.
I can get it to trigger if I change infiniteScrollUpDistance to 8, but that isn't ideal to have it requesting more items after only 20%.

ping. It would be great to get this working

Was this page helpful?
0 / 5 - 0 ratings