Skip to content

fix(dashboards-ng): make toolbar buttons responsive - #1820

Open
chintankavathia wants to merge 1 commit into
mainfrom
fix/dashboards-ng/toolbar/responsive
Open

fix(dashboards-ng): make toolbar buttons responsive#1820
chintankavathia wants to merge 1 commit into
mainfrom
fix/dashboards-ng/toolbar/responsive

Conversation

@chintankavathia

@chintankavathia chintankavathia commented Apr 6, 2026

Copy link
Copy Markdown
Member

currently when screen width is less toolbar action buttons and cancel/save buttons wraps and stack on each other without any spacing.

BEFORE:
image

AFTER:

image

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a responsive toolbar feature for the dashboard by integrating the SiAutoCollapsableListDirective and adding an overflow menu for actions that do not fit in the available space. I have identified a high-severity issue where an incorrect method name is used for checking visibility, and a medium-severity issue regarding the hardcoded aria-label which should be internationalized. Additionally, please ensure the component adopts the ChangeDetectionStrategy.OnPush strategy as required by the project style guide.

currently when screen width is less toolbar action buttons and cancel/save buttons wraps and stack on each other without any spacing.
@chintankavathia
chintankavathia force-pushed the fix/dashboards-ng/toolbar/responsive branch from efb3e68 to aef9dcd Compare April 6, 2026 09:45
@chintankavathia
chintankavathia marked this pull request as ready for review April 7, 2026 07:53
@chintankavathia
chintankavathia requested review from a team as code owners April 7, 2026 07:53
@spike-rabbit

Copy link
Copy Markdown
Member

@panch1739 please have a look here. I am not sure if this is the ideal responsive behavior

@spike-rabbit
spike-rabbit requested a review from panch1739 April 7, 2026 11:51

@panch1739 panch1739 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spike-rabbit @chintankavathia i think is a bit strange that only one action gets inside the menu. Could it be possible to collapse all actions in the menu, and only leave save/cancel visible?

@chintankavathia

chintankavathia commented Apr 9, 2026

Copy link
Copy Markdown
Member Author

@spike-rabbit @chintankavathia i think is a bit strange that only one action gets inside the menu. Could it be possible to collapse all actions in the menu, and only leave save/cancel visible?

@panch1739 It is dynamic in nature so if the view shrinks more then other action will also move into the menu.

image
image

@panch1739

Copy link
Copy Markdown
Member

@spike-rabbit @chintankavathia i think is a bit strange that only one action gets inside the menu. Could it be possible to collapse all actions in the menu, and only leave save/cancel visible?

@panch1739 It is dynamic in nature so if the view shrinks more then other action will also move into the menu.

image image

@chintankavathia ahhh ok, thanks for clarifying! Mmm i'm wondering if we should collapse all actions in the menu, even if there is space...just leaving save/cancel outside. @spike-rabbit WDYT?

@spike-rabbit

Copy link
Copy Markdown
Member

@panch1739 I think that would make sense. Then it is also aligend with the cab

@spike-rabbit spike-rabbit left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chintankavathia please try to build the suggestion by @panch1739

@spike-rabbit spike-rabbit added this to the 51.x milestone Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants