Input.ChoiceSet (filtered, multiselect): Selected chips truncate text with no tooltip on hover in Teams

Question

Input.ChoiceSet (filtered, multiselect): Selected chips truncate text with no tooltip on hover in Teams

Geete, Mayank 0

When using Input.ChoiceSet with isMultiSelect: true and style: "filtered", selected values render as compact pill/chip elements. For choices with longer titles, the text is heavily truncated (e.g., (ABC) Contoso Gl...), making it difficult — sometimes impossible — for users to distinguish between similar items.

There is no tooltip on hover over the chips in the Microsoft Teams desktop client, so users have no way to see the full title of a selected value.

Reproduction

Adaptive Card JSON:

{

"type": "AdaptiveCard",

"version": "1.5",

"body": [

{

  "type": "Input.ChoiceSet",

  "id": "products",

  "isMultiSelect": true,

  "style": "filtered",

  "choices": [

    { "title": "(ABC) Contoso Global Equity Fund Class A", "value": "1" },

    { "title": "(ABCX) Contoso Global Equity Fund Class Z", "value": "2" },

    { "title": "(DEF) Contoso Dynamic Allocation Fund Class A", "value": "3" },

    { "title": "(DEFX) Contoso Dynamic Allocation Fund Class Z", "value": "4" },

    { "title": "(GHI) Contoso Recovery Fund Class A", "value": "5" }

  ],

  "value": "1,2,3,4,5"

}
```  ],

  "actions": [{ "type": "Action.Submit", "title": "Submit" }]

}

**Steps**:

1. Render the above card in Microsoft Teams

2. Observe the selected chips — titles are truncated

3. Hover over any chip — no tooltip appears

**Expected behaviour**

- **Minimum**: A tooltip should appear on hover showing the full title text of the selected choice

- Ideal: Provide a property to control chip rendering, such as:

- > chipLayout: "wrap" — display chips on separate rows with full/longer text

- > maxHeight on the chip container — allow vertical scrolling when many items are selected

- > Or increase the default width allocated to each chip

**Actual behaviour**

- Chips truncate text after ~12-15 characters with ellipsis

- No tooltip on hover

- Users cannot distinguish between similarly named items (e.g., multiple fund classes with the same prefix)

**Environment**

- Host app: Microsoft Teams Web client and Windows desktop app

- Adaptive Card schema version: 1.5

- Card context: Bot-sent Adaptive Card with msteams.width: "Full"

**Impact**

This is a significant usability issue for enterprise scenarios where choice titles contain product codes, long identifiers, or hierarchical names. Users are forced to guess which truncated chip represents which item, leading to errors.

**Suggested solutions**

- Add tooltip on hover — lowest effort, highest impact

- Add a chipStyle or chipLayout property — gives card authors control over chip display

- Increase default chip width or allow chips to wrap to a second line showing more text

0 comments

2 answers

Your answer

Answer 1

Hi @Geete, Mayank

Dealing with aggressive text truncation on UI elements is incredibly frustrating, especially in enterprise scenarios where users rely on long product codes or hierarchical names to make accurate selections.

I have reproduced this exact scenario in my own environment using your provided JSON, and I am experiencing the exact same behavior. The chips are cutting off after roughly 15 characters, and hovering over them yields no tooltip whatsoever.

After digging into the current Adaptive Card schema (up through versions 1.5 and 1.6), I found that there are currently no properties available to control how these chips render. There are no options for chip layout (like wrapping), chip width, or setting tooltips for individual selected items. While version 1.5 did introduce a tooltip property, it is strictly limited to Action elements and cannot be applied to Input or Choice elements.

At this time, the best path forward is to get this in front of the product engineers. I highly encourage you to submit your detailed report directly to the official Adaptive Cards GitHub repository.

Reporting this on GitHub is the most effective way to flag this usability gap to the experts who design the schema, allowing them to provide further insights or log it as an official feature request.

I hope this helps point you in the right direction to get this UI gap addressed!

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Geete, Mayank 0 Reputation points

2026-04-09T06:39:40.6866667+00:00

Hi Michelle, thank you for the investigation and your response.
As suggested, I have raised this on the Adaptive Cards GitHub
https://github.com/microsoft/AdaptiveCards/discussions/9367
Michelle-N 14,470 Reputation points Microsoft External Staff Moderator

2026-04-09T13:48:33.13+00:00

Hi @Geete, Mayank

Thank you for your update. I hope this request will be considered soon.

Answer 2

The behavior described is a limitation of the current Input.ChoiceSet implementation in Microsoft Teams when using style: "filtered" with isMultiSelect: true. The Adaptive Cards schema and Teams documentation in the provided context do not define any properties to:

Control chip width or layout,
Enable wrapping of the selected-value chips,
Or configure a tooltip for the selected chips.

From the documented schema:

Input.ChoiceSet supports style values "compact", "expanded", and "filtered" (for typeahead search), plus standard properties like choices, isMultiSelect, value, placeholder, wrap, spacing, and separator.
Input.Choice only exposes title and value.
The Teams typeahead documentation adds choices.data and style: "filtered" for dynamic search, but does not introduce any chip-specific layout or tooltip properties.

No property in the schema or Teams-specific guidance allows changing how selected items are rendered as chips, including truncation behavior or hover tooltips. The layout and truncation of the chips are controlled entirely by the host (Teams) and are not configurable via Adaptive Card JSON.

Given the available documentation, there is no supported way to:

Show a tooltip with the full title on hover over the selected chips,
Make the chip text wrap instead of truncating,
Increase chip width, or
Switch to an alternative chip layout via something like chipLayout or chipStyle.

The only options within the documented capabilities are to adjust the choice titles themselves (for example, shortening or reordering text so the most distinguishing part appears first) or to use a different style such as "expanded" (rendering as checkboxes) if that better fits the scenario, accepting the different UX.

For feature-level changes such as tooltips, chip layout, or wrapping behavior, this would need to be handled as a product/feature request for the Teams Adaptive Cards host implementation rather than something that can be solved via current schema properties.

References:

Ashlesha Pawar (Tata Consultancy Services Limited) 75 Reputation points Microsoft External Staff

2026-04-08T10:24:06.96+00:00

Hi Geete, Mayank

We noticed the issue you raised regarding truncated chips in Input.ChoiceSet with style: "filtered" and isMultiSelect: true in Teams. An AI-generated answer suggested that currently there is no property in Adaptive Card JSON or Teams-specific schema to control chip width, wrapping, or hover tooltips. The recommended workarounds were:

Shorten or reorder choice titles so distinguishing parts appear first.

Use style: "expanded" (checkboxes) instead of filtered, if that fits your scenario.

Could you confirm whether these suggestions are feasible or helpful in your scenario? Or is the limitation still blocking your use case?

Thanks!
Ashlesha Pawar (Tata Consultancy Services Limited) 75 Reputation points Microsoft External Staff

2026-04-09T05:50:05.2166667+00:00

Geete, Mayank,

Just following up on the answer I shared recently. Could you please let me know if it resolved your issue, or if you need any further clarification?
Geete, Mayank 0 Reputation points

2026-04-09T06:53:31.23+00:00

Hi Ashlesha,

Thank you for the investigation and the detailed response.

To clarify our scenario: since Input.ChoiceSet does not support full text display in style: "filtered" with isMultiSelect: true, we are already using a Code + Display Value approach so users can identify the correct record despite truncation. Shortening or reordering the text is therefore not feasible, as both values are required for correct identification.

Using style: "expanded" is also not a viable option for us, as we rely on dynamic, backend-driven search, which is essential and not supported effectively with the expanded style.

Given these constraints, the limitation is still blocking our use case. For visibility, I’ve also raised this issue in the Adaptive Cards GitHub repository to track it more formally and gather broader feedback.

https://github.com/microsoft/AdaptiveCards/discussions/9367

Please let us know if there are any alternative approaches planned or under consideration to address this limitation.

Share via

Input.ChoiceSet (filtered, multiselect): Selected chips truncate text with no tooltip on hover in Teams

2 answers

Your answer