Secondary actions in adaptive cards broken for channel conversation
I have a strange behaviour in teams where an adaptive card is rendered differently depending on if the bot is posting it in a chat or in a teams channel. The adaptive card (reduced to the absolute minimum): { "contentType": "application/vnd.microsoft.card.adaptive", "content": { "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4", "body": [ { "type": "TextBlock", "text": "Intro text" }, { "type": "ActionSet", "actions": [ { "type": "Action.Submit", "title": "Set due date" }, { "type": "Action.Submit", "title": "Secondary option", "mode": "secondary" } ] } ] } } When the bot sends it into a chat, the rendering of the secondary action looks like that (expected behaviour): When it sends a message into a channel, the secondary option is rendered like that: There is a rectangle in front even though there is no image specified. Adding an icon to the action makes it even worse. The icon is not rendered properly but totally blown out of proportion. Is this a bug? Is there maybe a parameter that would prevent this rendering?
SameSite cookie problems in deskop version of Teams
Hi, I have created a Teams app, which contains static tabs (i.e. "personal" tabs). The tab content is hosted in SharePoint and uses MSAL v1.4.14 for authentication. However, I'm seeing the following "sameSite" cookie problems: Because a cookie's SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which will prevents the cookie from being set in a cross-site context in a future version of the browser. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery. Resolve this issue by updating the attributes of the cookie: Specify SameSite=None and Secure if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the Secure attribute. Specify SameSite=Strict or SameSite=Lax if the cookie should not be set by cross-site requests This problem only occurs in the Windows desktop version of Teams. I don't see it when I use Teams within a browser. I cannot find any information on how to fix this problem. Is it a bug in the desktop version of Teams and/or the MSAL library? I found the following: https://docs.microsoft.com/en-us/microsoftteams/platform/resources/samesite-cookie-update#samesite-cookie-attribute-2020-release but I am not sure how I can fix my problem. Here are some images of the errors I am seeing: Thanks, George
