-
Notifications
You must be signed in to change notification settings - Fork 104
AnalyticalTable: in hierarchical tree view, node and leaf items at the same level are not vertically aligned #5478
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 @ehn-sap thanks for reporting! The linked PR will fix the issue. Since the rows should be displayed flat, I would recommend using the "Compact" content density mode and not to fall below the standard height of 34px. This ensures that all elements (such as the expand button) are displayed according to the design specifications and that there are no unintended overflows or other side-effects. I've also added a note to the |
Thanks a lot @Lukas742 for the quick fix and the recommandation, we're going to check that with our PE and UX. |
Oops, I also wanted to add a example of setting the content density, but forgot to add the link. Here you go: https://stackblitz.com/edit/github-wmaqyf?file=src%2FMockData.ts,index.html,src%2FApp.tsx |
🎉 This issue has been resolved in version v1.26.0 🎉 The release is available on v1.26.0 Your semantic-release bot 📦🚀 |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Nodes (items having sub-items) and leaves (having no descendant) are differently indented.
Isolated Example
https://codesandbox.io/p/sandbox/analyticaltable-tree-view-lz23r3
Reproduction steps
In the provided screenshot, one can believe that item_3 is a child of item_2, but they are siblings.
Expected Behaviour
Item Labels (of node items and leaf items) at the same level in a hierarchy should be vertically aligned.
Screenshots or Videos
UI5 Web Components for React Version
latest
UI5 Web Components Version
latest
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
No response
Declaration
The text was updated successfully, but these errors were encountered: