microsoft / microsoft/AdaptiveCards

[Rendering] FactSet in AdaptiveCard renders incorrect

Open
#8,614 0 comments 0 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

1.0

Application Name

Microsoft Teams

Problem Description

During posting a message with AdaptiveCard in MicrosoftTeams (using my bot), FactSet element is rendering as a table with visible borders.
If I'll post the same AdaptiveCard using Power Automate - everything will be fine.

Screenshots

Current behaviour:
image

How its rendering in AdaptiveCard designer:
image

Card JSON
{
    "type": "AdaptiveCard",
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.0",
    "body":
    [
        {
            "type": "FactSet",
            "separator": true,
            "facts":
            [
                {
                    "title": "Site:",
                    "value": "New York (Demo)"
                },
                {
                    "title": "Start Date:",
                    "value": "03/03/2015 ( 8 years, 4 months and 11 days )"
                }
            ]
        }
    ]
}
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

The issue provides no repository file, test, or entry point. Start by reproducing the supplied AdaptiveCard JSON in Microsoft Teams and compare its FactSet rendering with the Adaptive Card designer; done means the FactSet no longer displays unintended visible borders.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.