-
Notifications
You must be signed in to change notification settings - Fork 229
Scrolled is not fired. #449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yep. I got this bug too |
Yes, we have the same :( |
i experience the same, any updates on this? |
Same here. The changes done to support Angular 17 are only for standalone components. Please let us know if the issue is fixed |
I’ll see it later and answer |
Getting Same issue: |
What you can do is take the code and make necessary changes after
debugging properly.
I did the same and not it is working properly for all the cases.
…On Wed, 28 May 2025, 6:50 pm Sebastian Scholle, ***@***.***> wrote:
*sscholle* left a comment (orizens/ngx-infinite-scroll#449)
<#449 (comment)>
Getting Same issue:
Using Latest Angular. The given example is not triggering anything. I dont
know what to do.
—
Reply to this email directly, view it on GitHub
<#449 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATRASXHVPH22PAYL2EJ4BRL3AWZY7AVCNFSM6AAAAABTF6YF2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJWGMYTMNZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Scrolled event is not fired , When the data in the grid is rendered.
Note: Page is not reloaded.
And on second note when the data in element to which the scroll is applied is rendered ,
this.triggered.down is set to previous height only.
These may not effect when scrolled more than one ,but when we are scrolling for first time and then rendering the data in element , without reloading or rebinding the I nfinit scroll , then totaltoScroll and this.triggered.down become equal and then these prevent the scrolled event from being fire when we are scrolling the element.
Looking further for your prompt reply.
The text was updated successfully, but these errors were encountered: