Closed amegan closed 7 months ago
Hi, we followed your repro steps, and are able to partially reproduce this. The compose area does become unresponsive, but the rendering doesn't appear broken - and the application does not crash or hang. We will take this issue up. Are you in Insiders Ring, or using the production version of Outlook?
Hi, I am on insider fast but the issue has happened on prod as well. We originally received the issue last year with the customer's real signature and it is still happening. My sample might not be enough on happening the issue constantly but hopefully, you got something from it. Maybe a little bit more complicated signature design might help to reproduce the issue constantly.
@amegan We will go ahead with the partial repro of bug with compose area becoming unresponsive. We have added it to our backlog. Thanks for reporting this issue. We unfortunately have no timelines to share at this point.
Signature insertion usually replaces the inserted signature if it is called more than once. This signature insertion does not replace existing signature but insert another signature after we call
Office.context.mailbox.item.body.setAsync()
API.Expected Behavior
Signature replacement should replace existing signature even after we call
Office.context.mailbox.item.body.setAsync()
.Current Behavior
After we call
Office.context.mailbox.item.body.setAsync()
API even we set back the exact same HTML we got fromOffice.context.mailbox.item.body.getAsync()
, signature insertion does not replace existing signature but insert another signature .And if the signature contains an image inside the table and has a text with empty lines after the table, the message composing pane becomes unresponsive to the user edit and eventually hangs after signature replacement.
Steps to Reproduce, or Live Example
Signature replacement not working
App unresponsive
Context
Our plugin keeps monitoring the composing body and updates the composing body using
body.setAsync()
. The user typically sets a default signature but sometimes wants to use a different one. After our plugin callsbody.setAsync()
, selecting different signature breaks a message content. Especially, crashing with a certain type of signature affects a lot on customer experience. The crash issue was reported by our customer and I made it simpler to reproduce. Using a table for layout information including the company logo and put some text under it is a common type of it.Your Environment
Useful logs