microsoft / microsoft/BotFramework-WebChat
Ability to style flipper buttons in suggested actions
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem?
The flipper button in suggested actions cannot be fully styled:
- Button chrome (border, radius, etc.)
- Icon
Describe the suggestion or request in detail
Ability to style more aspect of the flipper button in suggested actions.
After discussion with designer:
- Suggested action buttons appearance: rectangular or circular
- Suggested action buttons color mode (per button): white, primary, accent, ghost
- Because this could be done on a per button basis, probably set in the activity, rather than set in style options
- Is it okay/possible to set style options via channel data?
- Flipper buttons appearance: rectangular or circular
- Flipper buttons color mode: light mode, or dark mode (today)
- Item alignment: icon + text, text + icon, text-only, icon-only
- Size: small, medium, large
- Layout style: horizontal, bubbles (vertical as reply bubbles)
Describe alternatives you have considered
Style through CSS is not trivial and could break from time to time due to DOM change (unless via CSS insertion point or custom CSS properties).
Additional context
Related to AzDO #3653452.
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the suggested-actions flipper-button implementation and its styling options; the issue names no files or tests. Review the proposed appearance, color mode, alignment, size, and layout requirements, including whether per-button values belong in activity or channel data. Done means these options are supported without relying on fragile DOM-specific CSS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100