Repository navigation
<List> component growing="Scroll" no longer triggers scroll events after upgrade to 2.9.0+ #11687
Description
Describe the bug
After upgrading to version @ui5/webcomponents-react 2.9.0 (and later), the component with growing="Scroll" no longer triggers the onLoadMore event as expected when the user scrolls to the bottom.
This functionality worked correctly in earlier versions (e.g., 2.8.x), but appears to have stopped functioning after the 2.9.0 update.
Isolated Example
https://stackblitz.com/edit/github-zpv869gt?file=package.json,src%2FApp.tsx,src%2Fmain.tsx
Reproduction steps
-
Use
<List growing="Scroll" onLoadMore={handleLoadMore}>...</List> -
Add enough items to require scrolling.
-
Scroll to the bottom.
-
Observe that the onLoadMore callback is not triggered.
Expected Behaviour
The onLoadMore event should be triggered when the user scrolls to the bottom of the list.
Screenshots or Videos
No response
UI5 Web Components for React Version
2.9.0
UI5 Web Components Version
2.9.0
Browser
Chrome
Operating System
MAC OS
Additional Context
Downgrading to 2.8.x restores the expected behavior.
No errors appear in the console.
Relevant log output
Organization
SAP SF
Declaration
- I’m not disclosing any internal or sensitive information.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
Lukas742 commentedon Jun 10, 2025
Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.
Valkanister commentedon Jun 10, 2025
Hello @SAP/ui5-webcomponents-topic-p
Please have a look and advise how to properly setup a ui5-list with growing=Scroll. It seems the event is no firing.
Kind regards,
Georgi
SAP Development Support
NakataCode commentedon Jun 17, 2025
Hi @sleric1024,
I created a playground example to test the behavior
I found that the load-more functionality works correctly with vanilla HTML/JS web components in the same scenario (List with growing="Scroll" inside a Dialog). The core ui5-list component appears to be functioning properly.
This suggests the issue might be React-specific rather than with the underlying web components themselves.
Could you also try creating an HTML-based web components example where the functionality doesn't work?
Best Regards,
Nikola
Lukas742 commentedon Jun 17, 2025
Hi @NakataCode
please remove the
classof theui5-dialogand set the content-density to "Cozy". Then the issue is reproducible in your example as well.stephen-schmith commentedon Jul 9, 2025
@NakataCode I can confirm that this issue is reproducible by following the minor modifications described by @Lukas742 (actually, I can reproduce it just by removing the
dialogclass name in the playground example). It's also reproducible internally here in SuccessFactors where most of our UI5 WC code is on 2.10.Can we get an update on this topic? This issue breaks important functionality for us.
NakataCode commentedon Jul 10, 2025
Hi @stephen-schmith,
Thanks for following up.
The issue is currently in progress — we've identified the root cause and are now working on finding the best solution. I’ll share an update here once we have more news.
Best regards,
Nikola
stephen-schmith commentedon Jul 10, 2025
Thanks for the update @NakataCode .
stephen-schmith commentedon Aug 5, 2025
@NakataCode @dobrinyonkov Do you have any update on this issue? We have an upcoming major release in a few weeks, and this would be a significant regression for SF. Also, do you know if there will be any plan to backport this fix to 2.10?
NakataCode commentedon Aug 12, 2025
Hi @stephen-schmith,
Apologies for the delayed reply, and thank you for your patience. @dobrinyonkov has implemented a fix for this issue #12087, which is currently going through review.
Once it’s merged, we’d recommend upgrading to a version that includes this fix so you can benefit from the improvement. If there’s anything that might block the upgrade, please let us know — we’ll be happy to help.
Best regards,
Nikola
fix(ui5-list): growing with scroll improved (#12087)
github-actions commentedon Sep 5, 2025
This issue has been closed. To reopen, just leave a comment!