microsoft / microsoft/AdaptiveCards

[Feature Request] Allow line wrap by default when rendering buttons vertically

Open
#6,198 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Design Discussion - Needed Request
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

What is the problem you are attempting to solve with this feature?

In Webchat, where action buttons are stacked upon each other, button text doesn't wrap which leads to ellipsis, making it unclear what a button might do, and providing a less than optimal user experience overall:

button text overflowing

A description of your proposed solution to the problem

It should be possible for a host application to configure Webchat so button text is wrapped.

What alternatives or workarounds have you considered

A workaround is available via CSS.

Proposed solution

Add a new parameter in HostConfig to allow the host application to request that button text be wrapped. This should only apply to buttons when they are stacked on top of each other, not when they are lined up on a single row. By default, button text would continue to be truncated to maintain backwards compatibility. The new behavior would be opt-in.

QUESTION: Could we simply modify the default behavior and always wrap?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the Webchat button-rendering behavior and the HostConfig entry point mentioned in the request. Determine how an opt-in setting can affect only vertically stacked buttons while preserving truncation for single-row buttons and the default behavior; done means the configured wrapping works without changing existing defaults.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.