A repo and NPM package for Office.js, corresponding to a copy of what gets published to the official "evergreen" Office.js CDN, at https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
Provide required information needed to triage your issue
Foreign characters stopped working in the Outlook 365 client when inserting signatures with OnNewMessageCompose event.
It appears the issue is only present in the current channel.
If I roll back to the monthly channel, it still works as expected.
Your Environment
Platform [PC desktop, Mac, iOS, Office on the web]: PC desktop
Host [Excel, Word, PowerPoint, etc.]: Outlook 365 (Client)
Office version number: 2312
Operating System: Windows 10/11
Browser (if using Office on the web): N/A
Expected behavior
The foreign characters "Æ", "Ø" and "Å" are expected to be shown correctly.
Current behavior
I open a new mail and the OnNewMessageCompose event is fired as expected. Afterwards my signature is inserted, but I get weird characters instead of the expected letters. If I fire the same event manually, the foreign characters are shown correctly.
Steps to reproduce
Open Outlook Client
Start a new mail
When the signature is inserted through our add-in, the characters are broken.
Context
The issue has been present ever since the current channel was updated in january.
Useful logs
[ ] Console errors
[X] Screenshots
[ ] Test file (if only happens on a particular file)
Provide required information needed to triage your issue
Foreign characters stopped working in the Outlook 365 client when inserting signatures with OnNewMessageCompose event. It appears the issue is only present in the current channel. If I roll back to the monthly channel, it still works as expected.
Your Environment
Expected behavior
The foreign characters "Æ", "Ø" and "Å" are expected to be shown correctly.
Current behavior
I open a new mail and the
OnNewMessageCompose
event is fired as expected. Afterwards my signature is inserted, but I get weird characters instead of the expected letters. If I fire the same event manually, the foreign characters are shown correctly.Steps to reproduce
Context
The issue has been present ever since the current channel was updated in january.
Useful logs
How it looks:
How it is supposed to look: