You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.
I needed for my app to support full page scrolling so I've modified your directive to support "target" attribute. (Sorry I don't have time to do a PR). The following code supports both scrolling an element other than the current one (if you use routes and need to target a parent) and the special case of the whole page scrolling - 'window'.
I would also love to be able to listen to the full page scroll position. However, this method doesn't work so well when using the angular routing features. Each time you navigate away and then back to the route that contains the infinite scroll directive, a new scope is created for the directive resulting in multiple listeners calling your handler. I'm not sure if this is a symptom of lrInfiniteScroll, itself or this gist.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I needed for my app to support full page scrolling so I've modified your directive to support "target" attribute. (Sorry I don't have time to do a PR). The following code supports both scrolling an element other than the current one (if you use routes and need to target a parent) and the special case of the whole page scrolling - 'window'.
Full code is in this gist: https://gist.github.com/SimeonC/a15055a5b9ec0c5685da.
Highlights below:
Inserted at Line 12:
Line 35:
The text was updated successfully, but these errors were encountered: