-
Notifications
You must be signed in to change notification settings - Fork 273
[SF][Table]: Table will scroll to top when fitst time loadmore #11298
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
Hi @yuyuCream I wasn't able to reproduce this issue (Chrome Version 134.0.6998.167), so please add an isolated example that is showing the issue. Preferably by using this StackBlitz template. 2025-04-08_09-27-34.mp4 |
Hi @Lukas742 Additionally, I found an error in the example: even if the type is set to scroll in the DOM, there is still a 'more' button in the table. |
Hi @yuyuCream that's why we ask for an isolated example. Please provide it then we can process the issue further. |
Hi @Lukas742 |
@yuyuCream I was finally able to reproduce the issue, but the behavior seems to be flaky because I needed some tries before it occurred. Since the Hi Colleagues, 2025-04-10_13-10-23.mp4 |
Hello colleagues, Steps to reproduce:
Could you please take over? Regards, |
This issue has been closed. To reopen, just leave a comment! |
🎉 This issue has been resolved in version v2.10.0-rc.2 🎉 The release is available on v2.10.0-rc.2 Your semantic-release bot 📦🚀 |
Describe the bug
The table will scroll to the top and focus on the first line when the "onLoadMore" is triggered for the first time by scrolling down. For subsequent "onLoadMore" triggers, if a different line is selected, the table will also scroll to the top and focus on the first line.
Isolated Example
No response
Reproduction steps
This issue only occurs in version 2.0 and works fine in version 1.0.
Expected Behaviour
No response
Screenshots or Videos
No response
UI5 Web Components for React Version
2.8.0
UI5 Web Components Version
2.8.0
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
Organization
SF
Declaration
The text was updated successfully, but these errors were encountered: