microsoft / microsoft/AdaptiveCards

[Rendering] Full Width Adaptive Cards Stopped Working (Again!)

Open
#9,394 3 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Renderers Bug
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Target Platforms

Other

SDK Version

26213.1006.5014.9784

Application Name

Microsoft Teams

Problem Description

Full width Adaptive Cards stopped working again. MS Teams version 26213.1006.5014.9784

I don't know what the f*ck you guys do at MicroSlop. We have been fighting this bug since 2022. Don't you assclowns check this before each deployment?

All of our Adaptive Cards content are squished.

Screenshots

No response

Card JSON
{
	"type": "AdaptiveCard",
	"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
	"version": "1.4",
	"msTeams": {
		"width": "full"
	},
	"body": [
		{
			"type": "Container",
			"spacing": "none",
			"items": [
				{
					"type": "TextBlock",
					"text": "Content Squished",
					"color": "good",
					"spacing": "none",
					"weight": "bolder",
					"size": "medium",
					"wrap": true
				},
				{
					"type": "FactSet",
					"facts": [
						{
							"title": "Title",
							"value": "MicroSlop"
						},
						{
							"title": "Message",
							"value": "AI Slop"
						}
					]
				}
			]
		}
	]
}
Sample Code Language

No response

Sample Code

No response

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 reproducing the provided Adaptive Card JSON in Microsoft Teams version 26213.1006.5014.9784 and compare its layout with the expected full-width behavior. Done means the card content is no longer squished and the msTeams.width setting renders as full width.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.