The text issue is being solved now in T310158: Button, ButtonGroup: solve max-width and text issues.

Possible solutions to avoid the Button text to be cut off when it exceeds the available space are:

After creating this prototype to test how the Container is used, we've found that the Container alone doesn't address all the layout issues, particularly how columns scale and respond to different screen sizes. After discussing with @Volker_E, we've decided to focus on a new branch that integrates both the Container and the Grid (currently being worked in this proof-of-concept) so we can check how Container and Grid solve this issues when combined together.

El T310158#10662110, @CCiufo-WMF escribió:

I actually think we should apply ellipses on overflow as part of this task. The centering of long text in the button (shown in your screenshot) is more confusing than truncating with ellipses because you don't get the context for the beginning of the text. I would suggest we merge T337865 into this task, so buttons behave the same way as InfoChip and InputChip in T388857. We can figure out the tooltip part later in T364928.

To prevent Button’s max-width from causing issues in narrow containers, we discussed updating it to 100% to ensure the Button can expand based on its content and fully fill the container when needed. I’ve worked on this patch (demo) to update the Button and ToggleButton max-width to @size-full.

I've updated the max-width of both InfoChip and InputChip to @size-full to adapt to the width of their container. This will address the issue highlighted in this task T373747: ChipInput: Chips with long aliases overflow from the border input box. Check the demo.

To ensure consistency between InfoChip and the InputChips used within ChipInput and avoid issues with text length, we've decided on removing the current 512px max-width from both components. This will allow them to expand as needed based on the text length.

@Volker_E the ProgressIndicator component and guidelines look good. Thank you!

Included font size modes in the Codex Figma library:

El T386997#10635269, @Volker_E escribió:

@bmartinezcalvo Please sign-off on the "The component follows the Container design specs" acceptance criteria.

We included a section for "When to use" each component in Codex, clarifying when to use TypeaheadSearch or Lookup so I guess we can solve this task @AnneT

We already updated the Tip messages in Codex to be the most similar to our Codex Message. I guess we can solve this task. @AnneT could you confirm?

@AnneT I think we can solve this task since all components include now a Configurable demo. Just Link is missing that, but I guess it's not possible to include a Configurable demo there.

Solving this task since we already included a Light/Dark mode selector in Codex.

Solving this task since we no longer document guidelines in Figma. This is documented in Codex > Style Guide > Typography.

This was already solved.

This has been solved while working on T363845: [EPIC] Typography scale and font sizing so I guess we can solve this task. @DTorsani-WMF please confirm.

Solving this task since the Thumbnail is using cdxIconImage as requested in this task.

I think this is being solved while working in T363845: [EPIC] Typography scale and font sizing so I guess we could solve this task. @DTorsani-WMF could you confirm?

Solving this task since the inconsistencies listed have been solved, will be solved in other tasks, or are no longer needed.