Description: I often work with documents that include a 'watermark' image, such that the image itself is formatted to be transparent and in the background of the page. I can edit, and save, this kind of image formatting with no problems in *.odt documents, but the changes never save in *.docx documents. Steps to Reproduce: 1. Take *.docx document with image transparency formatted into a part of the document 2. Open using LibreOffice 3. Actual Results: The image with some percentage of transparency appeared as if it had no transparency. Expected Results: The image formatting should stay the same, whether the document is being worked on in Microsoft Office or LibreOffice. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info:
Created attachment 145887 [details] Logo originally transparent in *odt. Pasted and saved in this *.docx, but transparency not saved.
Bug confirmed. Version: 6.3.0.0.alpha0+ (x64) Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684 CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55 Locale: zh-TW (zh_TW); UI-Language: en-US Calc: threaded
Set to NEW because of comment 2
Hello BVZ, Could you please attach the original .ODT file? Otherwise, we can't investigate this issue. I have set the bug's status to 'NEEDINFO'. Please change it back to 'NEW' once the requested document is provided.
Hi Xisco, Thanks for looking into this. The problem actually does not concern image transparency when working in *.odt files, this feature works as intended. The problem is when one tries to save image transparency in *.docx files, closes said file with image transparency setting, then reopens that same file. The 'saved' image transparency does not appear as saved and the image only appears with its initial opacity.
Hello BVZ, Yes, i know, that's why I'm asking for the original .ODT to investigate the conversion from .ODT to .DOCX
Created attachment 147490 [details] ODT original
Hi Xisco, I see, understood and uploaded. Also FYI, I did some other photo editing saved to .docx recently and none of it saved when I reopened the document. These issues didn't involve transparency, but possibly related since they are about saving in .docx.
I confirm it with attachment from comment 8 and Version: 6.2.0.0.beta1 (x64) Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (de_DE); UI-Language: en-GB Calc: threaded and Version: 5.4.7.2 (x64) Build-ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU-Threads: 4; BS: Windows 6.19; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: CL
*** Bug 134356 has been marked as a duplicate of this bug. ***
Dear BVZ, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in Version: 25.2.4.3 (X86_64) / LibreOffice Community Build ID: 33e196637044ead23f5c3226cde09b47731f7e27 CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Steps: 1. Open attachment 147490 [details] 2. save as docx and reload Actual result Transparency gets lost Expected result Transparency should be remained