You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow specifying adaptive elements for the toggles and choice sets. That way, when authors also want to control the text size, or max lines, or use images, we don't have to add new properties for each of those - we already have those properties on TextBlock, etc.
Schema
New property on Input.Toggle and Input.ChoiceSet
Property
Type
Required
Description
content
AdaptiveElement
false
A rich adaptive element to be displayed instead of the string-based title.
Example
{
"type": "Input.Toggle",
"title": "This is a very long title",
"content": {
"type": "TextBlock",
"text": "This is a very long title",
"wrap": true
}
}
Host Config
No changes.
Down-level impact
Low. The rich content doesn't get displayed, but it never did anyways. The title is a required property, so authors will always have to provide it, so their cards will still work well down-level even if they're not explicitly designing for it.
Host burden
None. Renderer handles it all.
Renderer Requirements
A renderer should display the content instead of the title if possible.
The text was updated successfully, but these errors were encountered:
Proposal approved. Note however that we need to look at priorities and see if we should do this in 1.2 or not, since the text wrapping feature is being handled by a more simple proposal of just adding a wrap property. So this feature would specifically be solving requests for richer content.
andrewleader
changed the title
Proposal: Support adaptive elements for title of ChoiceSet/Toggle
Spec draft: Support adaptive elements for title of ChoiceSet/Toggle
Oct 3, 2018
Solves requests
Summary
Allow specifying adaptive elements for the toggles and choice sets. That way, when authors also want to control the text size, or max lines, or use images, we don't have to add new properties for each of those - we already have those properties on TextBlock, etc.
Schema
New property on
Input.Toggle
andInput.ChoiceSet
Example
Host Config
No changes.
Down-level impact
Low. The rich content doesn't get displayed, but it never did anyways. The title is a required property, so authors will always have to provide it, so their cards will still work well down-level even if they're not explicitly designing for it.
Host burden
None. Renderer handles it all.
Renderer Requirements
content
instead of thetitle
if possible.The text was updated successfully, but these errors were encountered: