Change Details

In T359636, one of the approaches to handle content overflow is to use ellipses when it is important to maintain a consistent component height. This will be needed for Buttons (T337865), Selects (T347621), and other components like ChipInputs. The suggested method for providing the full text content to users is through a tooltip, which should be the Codex Tooltip (T340456) but could be the browser default tooltip until the Codex version is available. Acceptance Criteria [] Determine if ellipsis truncation can be reliably used for truncation in Codex components [] Determine if the same approach to ellipsis truncation can be used for all components [] Determine if a Tooltip can reliably be rendered on hover when text is truncated using an ellipsis

In T359636, one of the approaches to handle content overflow is to use ellipses when it is important to maintain a consistent component height. This will be needed for Buttons (T337865), Selects (T347621), and other components like ChipInputs. The suggested method for providing the full text content to users is through a Tooltip. We need to ensure that we can reliably automatically apply ellipses truncation in these situations. We also need to ensure using a Tooltip to display the full Button label does not present any accessibility issues, particularly on touchable screens where the hover is not possible. There has been feedback in T337865#9861972 that the content overflow approach should avoid using ellipses in Buttons, which we can evaluate once we have a working version. Acceptance Criteria [] Determine if ellipsis truncation can be reliably used for truncation in Codex components [] Determine if a Tooltip can reliably be rendered when text is truncated using an ellipsis, including on touch devices [] Decide if using ellipses for Button labels is still the best UX

In T359636, one of the approaches to handle content overflow is to use ellipses when it is important to maintain a consistent component height. This will be needed for Buttons (T337865), Selects (T347621), and other components like ChipInputs. The suggested method for providing the full text content to users is through a tooltipTooltip. We need to ensure that we can reliably automatically apply ellipses truncation in these situations. We also need to ensure using a Tooltip to display the full Button label does not present any accessibility issues, particularly on touchable screens where the hover is not possible. There has been feedback in T337865#9861972 that the content overflow approach should avoid using ellipses in Buttons, which should be the Codex Tooltip (T340456) but could be the browser default tooltip until the Codexwe can evaluate once we have a working version is available. Acceptance Criteria [] Determine if ellipsis truncation can be reliably used for truncation in Codex components [] Determine if the same approach to ellipsa Tooltip can reliably be rendered when text is truncation can be used for all componentsed using an ellipsis, including on touch devices [] DeterminDecide if a Tooltip can reliably be rendered on hover when textusing ellipses for Button labels is truncated using an ellipsisstill the best UX