Closed andregloeckner closed 5 months ago
Hi @andregloeckner , thanks for reaching us.
We'd like to know that which plateform does the issue occurs? Win32 or Word Online?
Thanks.
Hi @andregloeckner , thanks for reaching us.
We'd like to know that which plateform does the issue occurs? Win32 or Word Online?
Thanks.
Its the Microsoft Office 365 Professional Plus (32Bit) Windows installation.
@andregloeckner Currently, I cannot reproduce it on my side. Could you provide your Word build version(Word-account) and send your original Word document to my mailbox haijiajin@microsoft.com.
@andregloeckner Currently, I cannot reproduce it on my side. Could you provide your Word build version(Word-account) and send your original Word document to my mailbox haijiajin@microsoft.com.
I send an email with the required details.
Thanks @andregloeckner. We have opened an internal bug #8274322 to track it. We'll back to you if there are any updates.
Hi @andregloeckner, After confirmation, we had a fix regarding this issue a month ago. It is rolling out. From your Office build number, it seems you are in the SAC channel which updates every six months. The fix will deployed to SAC production in Jan 2024 if everything goes as usual. Thanks.
We want to load docx files from our cloud application and start to add login and load function in a react word add-in. Currently we fail because the loading of the file into the current Word window not map the correct paragraph.spaceAfter.
Different behavior loading a word file from byte[]. Try with the follow code blocks:
response.data.content
is our byte[]When open a docx file as byte[] to new Word with that code block, the format is fine.
When open a docx file as byte[] to current Word instance with that code block, it looks wrong.
Provide required information needed to triage your issue
Your Environment
package.json "office-addin-cli": "^1.5.5", "office-addin-debugging": "^5.0.5", "office-addin-dev-certs": "^1.11.3", "office-addin-lint": "^2.2.5", "office-addin-manifest": "^1.12.3", "office-addin-prettier-config": "^1.2.0",
Expected behavior
Current behavior
When loading the byte[] with
When loading the byte[] into an new instance of Word with open()
Steps to reproduce
When open a docx file as byte[] to new Word with that code block, the format is fine.
When open a docx file as byte[] to current Word instance with that code block, it looks wrong.
When set the space manually after loading, it looks like more expected. But this is very slow and not fit a dynamic configuration of that.