You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using renderRowSubComponent in AnalyticalTable the sub-row height is somehow not taken into account when rendering the table. Even if visibleRowCountMode is set to Auto, not all rows and sub-rows are displayed, but some are hidden and need scrolling.
To Reproduce
Steps to reproduce the behavior:
Open example
Expected behavior
All rows and sub-rows are shown and the table has the correct height.
Screenshots
UI5 Web Components for React Information @ui5/webcomponents version: 1.9.1. @ui5/webcomponents-react version: 1.6.0
Operating System: Windows
Browser: Chrome
Additional context
The text was updated successfully, but these errors were encountered:
This PR adds the `subComponentsBehavior` prop which accepts the
`AnalyticalTableSelectionBehavior` enum.
It enables controlling how subcomponents should be rendered and if they
should be considered when calculating the initial table body height.
`alwaysShowSubComponent` has been deprecated in favor of
`subComponentsBehavior`.
Fixes#3862
---------
Co-authored-by: Marcus Notheis <[email protected]>
Describe the bug
When using renderRowSubComponent in AnalyticalTable the sub-row height is somehow not taken into account when rendering the table. Even if visibleRowCountMode is set to Auto, not all rows and sub-rows are displayed, but some are hidden and need scrolling.
Isolated Example
Please provide an isolated example if possible by forking this codesandbox.
https://codesandbox.io/s/sharp-fog-5vj47w?file=/src/App.js
To Reproduce
Steps to reproduce the behavior:
Open example
Expected behavior
All rows and sub-rows are shown and the table has the correct height.
Screenshots
UI5 Web Components for React Information
@ui5/webcomponents
version: 1.9.1.@ui5/webcomponents-react
version: 1.6.0Operating System: Windows
Browser: Chrome
Additional context
The text was updated successfully, but these errors were encountered: