TextBlock <-> TextRun parity

[productboard-ac]

Summary

All the relevant properties on TextRun should also be on TextBlock and vice versa

Requirements

• See summary

Spec/schema

After the proposal process, update this with a link to the spec PR.

Proposed changes

Added to TextBlock

• highlight

• italic

• selectAction

• strikethrough

• underline

Added to TextRun

• N/A

Example

{
    "type": "AdaptiveCard",
    "version": "1.0",
    "body": [
        {
            "type": "TextBlock",
            "text": "Strike me out",
            "strikethrough": true
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
}

Host Config

N/A

Down-level impact

Minimal. The new properties won't be respected down-level.

Host burden

N/A

[productboard-ac]

Link to feature: https://adaptivecards.productboard.com/feature-board/planning/features/2372634

[dclaux]

I personally vote against this. These properties will conflict with Markdown support, which is precisely why we decided that RichTextBlock would not support Markdown.

[andrewleader]

7/12/2019 review meeting

• David absent and Matt not sure, so postponing any decisions
• David joined, we're split half-half, moving on for now

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 5 days.