Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signature bookmark is lost in Outlook Desktop when new message is opened after recall #4457

Open
bogdanst24 opened this issue May 15, 2024 · 2 comments
Assignees
Labels
Area: Outlook Issue related to Outlook add-ins Needs: attention 👋 Waiting on Microsoft to provide feedback

Comments

@bogdanst24
Copy link

Provide required information needed to triage your issue

Your Environment

  • Platform [PC desktop, Mac, iOS, Office on the web]: PC Desktop
  • Host [Excel, Word, PowerPoint, etc.]: Outlook
  • Office version number: Version 2402 Build 16.0.17328.20282
  • Operating System: Windows

Expected behavior

When the new email window is opened, if a signature is already inserted, correctly detect it and have the setSignatureAsync API replace it.

Current behavior

When the new window after a recall is opened, the already inserted signature through setSignatureAsync is ignored and a second signature is inserted when using again the setSignatureAsync.

Steps to reproduce

  1. Send an email containing an email signature and recall it in Outlook desktop
  2. Choose the "Delete unread copies and replace with a new message" option. This will trigger the window to open with the editable recalled email.
  3. Use any way (events, manual from taskpane) to insert again the signature. Instead of replacing it, it will add a new one.

Provide additional details

This seems to happen in Outlook Desktop regardless of the method the signature was inserted. Probably the signature bookmark is lost, as properties are removed when sending the email. The issue can be reproduced also by using the native signature insertion.
I know it is not only related to web add-ins, but they are affected by this Outlook bug and customers put the blame on the web add-ins. It would be great at least to receive information regarding the acknowledgement of the bug.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label May 15, 2024
@exextoc exextoc added Needs: attention 👋 Waiting on Microsoft to provide feedback Area: Outlook Issue related to Outlook add-ins and removed Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP labels May 15, 2024
@exextoc exextoc self-assigned this May 15, 2024
@mmanjaree-msft
Copy link

Is the issue happening with new Outlook and owa or classic outlook?

@bogdanst24
Copy link
Author

Only classic Outlook. There is no such option on the recall on new Outlook/owa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Outlook Issue related to Outlook add-ins Needs: attention 👋 Waiting on Microsoft to provide feedback
Projects
None yet
Development

No branches or pull requests

3 participants