-
Notifications
You must be signed in to change notification settings - Fork 9
Description
Which component(s) are affected?
Tile Manager
Description
When a tile with the maximum row-span in a tile manager layout is maximized, and it is the only tile with that row-span, the tile manager container shrinks in height. This causes content in the maximized tile to be cut off.
Related to this behavior in the samples: IgniteUI/igniteui-angular-samples#3827
Reproduction
- Open
stories/tile-manager.stories.ts - Comment out the 'Products' Visualization from
orderDetailsVisualizationsarray (around line 520-526) - Run the stories and open the TileManager > Fin Dashboard story in Storybook
- Maximize the first tile (the tile with the list content)
- Observe that:
- The tile manager container height decreases significantly
- The list items in the maximized tile are cut off and not fully visible
- The grid height is now based only on the remaining tiles with smaller row-spans
Workaround
To avoid this issue, ensure there are at least two tiles with the maximum row-span value. When one is maximized, the other remains in the grid flow and maintains the grid height. This is demonstrated in the original FinDashboard story where the 'Products' tile (with rowSpan: 30) remains in the grid when other tiles are maximized, preventing the grid from shrinking.
Is this a regression?
No or unsure. This never worker, or I haven't tried before.
Affected versions
Failing in 6.3.6
Browser/OS/Node environment
N/A