Created attachment 163186 [details] docx sample with watermarks I have a DOCX with different VML watermarks. Only one of those is set to visible whereas the others have visibility "hidden" via a style property (can be seen in the /word/header2.xml). This is used by my software to invalidate documents in several ways. In the attached document there is "TEST"-watermark that should be shown. When opening this document in writer (or converting to PDF via unoconv) the "KEIN ORIGINAL" watermark is displayed and the TEST-watermark is not displayed (along with some other watermarks that really should not be shown too). The "KEIN ORIGINAL" watermark is special as it is grouped. So maybe the problem is in the handling of the group and the styles when importing this shape. You can see that the output differs in the PDFs I attached. The output of writer 7.1 (https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/2020-07-17_06.44.55/LibreOfficeDev_7.1.0.0.alpha0_Win_x64.msi) is the same. Expected behavior: The TEST-watermark should be shown. The "KEIN ORIGINAL"-watermark should not be shown.
Created attachment 163198 [details] Sample file
Hello rominator@gmx.at For future reports, please, attach each file separately if possible
Created attachment 163199 [details] Comparison MSO 2010 and LibreOffice 7.1 master
Reproduced in Version: 7.1.0.0.alpha0+ Build ID: d851a02df57ab378ed0cc6d9362516de09c3279c CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Version: 5.2.0.0.alpha1+ Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; Locale: ca-ES (ca_ES.UTF-8) Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Dear rominator, 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 repro Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 88d7aa8ab79b1197191b5eb24a3b67d313797026 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded