Skip to content

Conversation

@JPeer264
Copy link
Member

@JPeer264 JPeer264 commented Dec 1, 2025

The adjacent traces did have one tooltip for both buttons. To increase UX, they were split now into two:

Screenshot 2025-12-01 at 10 25 11

@JPeer264 JPeer264 requested a review from a team as a code owner December 1, 2025 09:42
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 1, 2025
}
)}
>
<div>
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Is this div needed, or would a Fragment be an alright replacement here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Great question. The div, or any other element is needed since the ButtonBar is centered by default (and the parent container is a little higher).

There are two solutions:

  • Either wrap it inside a div (or any other element)
  • Or update the style of ButtonBar and use a StyledButtonBar for this component. And "undo" the align-items: center

I went for the first, since there is a Omit<..., 'className'> on the ButtonBar - which is maybe there for a reason.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hrrm, alrighty sounds all good to leave as is to me 👍

Copy link
Member

@Lms24 Lms24 left a comment

Choose a reason for hiding this comment

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

Thanks!

size="xs"
icon={<IconChevron direction={iconDirection} />}
aria-label={ariaLabel}
tooltipProps={tooltipProps}
Copy link
Member

Choose a reason for hiding this comment

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

l (feel free to ignore): Should we inline the toolTipProps here and just adjust message based on direction? based from what I can tell the other props are the same in both cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants