-
Notifications
You must be signed in to change notification settings - Fork 103
AnalyticalTable: setting minWidth
for columns
causes unnecessary overflow
#7072
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 @Lukas742, @MarcusNotheis, The issue is related to AnalyticalTable so I'm forwarding it to ui5-webcomponents-react project. Hi @clevianerebeca-silva, |
hey @nnaydenow here is: https://stackblitz.com/edit/github-thk7nci8-znb8zkpk?file=src%2FApp.tsx. I basically set a higher minWidth for the first and last columns. Check it on a large screen that is wider than the sum of the minWidths, and you'll see that the horizontal scroll appears |
minWidth
for columns
causes unnecessary overflow
🎉 This issue has been resolved in version v2.9.2 🎉 The release is available on v2.9.2 Your semantic-release bot 📦🚀 |
Uh oh!
There was an error while loading. Please reload this page.
Bug Description
AnalyticalTable columns with minWidth are causing an unnecessary overflow
Affected Component
AnalyticalTable
Expected Behaviour
When we set minWidths for all columns and the table size is bigger than the sum of the minWidths, no overflow should happen.
Isolated Example
https://stackblitz.com/edit/github-thk7nci8-znb8zkpk?file=src%2FApp.tsx
Steps to Reproduce
...
Log Output, Stack Trace or Screenshots
Our AnalyticalTable usage:
Columns definition:
Screen.Recording.2025-03-12.at.16.49.23.mov
As you can see in the video, the table is 1197px wide, while the sum of the minWidths is 985px. Since there is available space, the horizontal scroll shouldn't appear. We also tried with
scaleWidthMode
as Grow and Smart but the overflow also happens in both cases.Priority
Low
UI5 Web Components Version
2.7.1
Browser
Chrome
Operating System
No response
Additional Context
No response
Organization
No response
Declaration
The text was updated successfully, but these errors were encountered: