Peter Lasne
Peter Lasne
**Describe the bug** This is not 100% reproducible because machines with 16 GB of RAM or less tend to reload the page on return. But, for those systems with more...
**Describe the bug** Receiving an emoji raises an error message in the Chat component... ``` react-dom.development.js:67 Warning: A component is `contentEditable` and contains `children` managed by React. It is now...
**Describe the bug** StatefulGraphChatClient creates 2 new GraphNotificationClients - in the constructor and when updateGraphNotificationClient is called. This starts 2 shared worker timers. There are a couple of pieces of...
[FEATURE] As an mgt-chat user I want urls in my chat messages to render as links in the Teams client
**Describe the bug** Sending a message containing a URL from mgt-chat will be received as a hyperlink in mgt-chat, but in Teams it will not be hyperlinked. Sending a message...
**Describe the bug** If you navigate between multiple chats (for instance, using ChatList) you can reach the subscription limit when returning to a chat. This also seems to cause "You...
**Describe the bug** When the person you are chatting with is an external user (someone outside your domain), the user name is Unknown. **To Reproduce** Steps to reproduce the behavior:...
**Describe the bug** It is possible for the Chat component to render messages multiple times. **To Reproduce** NOTE: You must have a fast way to switch chat threads. You can...
**Describe the bug** If chatting with a bot in a group chat, the name of the app/bot will not show next to the datetime and before the message. Unfortunately, this...
**Describe the bug** By switching quickly between chats, it is possible for messages from the wrong chat to be cached and shown. **To Reproduce** To reproduce this issue you need...
**Describe the bug** When receiving messages across multiple chats, those messages can get mixed up between the chats both in cache and on-screen. This is different than https://github.com/microsoftgraph/microsoft-graph-toolkit/issues/3031, though maybe...