When the person component is defined using person-details, the buttons in the person-card for chat, video and call are visible but not working on click.
Add this component in the html tab, replacing ccdev1@fresh.onmicrosoft.com with a valid email of a user in your organization:
<mgt-person person-details='{"displayName":"Frank Herbert1","jobTitle":"jobTitle","department":"department","id":"ccdev1@fresh.onmicrosoft.com"}' view="threelines" person-card="click" />
Note that the person component renders the name, department and job title indecated in the person-details object. In the screenshot above the name is Frank Herbert1.
Click the person component to open the person-card
Note that the person name, department and job title inside the card have been resolved with the actual values of the user indicated in the "id" attribute. In the screenshot above the actual name is "Ruth Bader Ginsburg".
Click the buttons chat, video and call and note that nothing happens.
Expected behavior:
chat, video and call buttons should work, opening the corresponding application
buttons that are not going to work should not be visible
Actual behavior:
chat, video and call buttons are not working
Workaround
I found a workaround by adding the properties userPrincipalName and businessPhones in the person-details object, but this should not be necessary as they can be obtained when the actual name is resolved. I think this was the case in previous versions of MGT.
Bug Report
Prerequisites
For more information, see the
CONTRIBUTING
guide.Description
When the person component is defined using person-details, the buttons in the person-card for chat, video and call are visible but not working on click.
Steps to Reproduce
<mgt-person person-details='{"displayName":"Frank Herbert1","jobTitle":"jobTitle","department":"department","id":"ccdev1@fresh.onmicrosoft.com"}' view="threelines" person-card="click" />
Expected behavior:
Actual behavior: chat, video and call buttons are not working
Workaround
I found a workaround by adding the properties userPrincipalName and businessPhones in the person-details object, but this should not be necessary as they can be obtained when the actual name is resolved. I think this was the case in previous versions of MGT.
<mgt-person person-details='{"displayName":"Frank Herbert2","jobTitle":"jobTitle","department":"department","id":"ccdev1@fresh.onmicrosoft.com","userPrincipalName":"ccdev1@fresh.onmicrosoft.com","businessPhones":["1234"]}' view="threelines" person-card="click" />