Created attachment 103740 [details] Attached file contain two images. Problem description: In attached file there are two images. In original file first image is behind of second image. But on LO rendered second image behind of first image and exported the same. Steps to reproduce: 1. Open attached file on latest LO master 2. Save file as docx file again. 3. Open saved file on MS Office Current behavior: Z-ordering is rendered/saved incorrectly. Expected behavior: LO should render and save z-order properly. Operating System: Ubuntu Version: 4.4.0.0.alpha0+ Master
Synerzip -> NEW
Created attachment 118043 [details] Comparison between Word 2010 (left) and Libreoffice 5.0.0.5 (right) Problem still present in Version: 5.0.0.5 Build ID: 1b1a90865e348b492231e1c451437d7a15bb262b Locale: es-ES (es_ES) on Windows 7 (64-bit)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
The problem is still present in Version: 5.4.0.0.alpha1+ Build-ID: 8c0be54a7da6262dffe04357121814dd22b5d7fe CPU-Threads: 4; Betriebssystem:Windows 6.1; UI-Render: Standard; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-15_01:35:45 Gebietsschema: de-DE (de_DE); Calc: group and in Version: 6.0.0.0.alpha0+ Build ID: 9f3814af7264ce90685a82cbf4eb015a38f22bf7 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-28_00:47:42 Locale: de-DE (de_DE); Calc: group It is an imported error.
The problem is still present in Version: 5.4.0.0.alpha1+ Build-ID: 8c0be54a7da6262dffe04357121814dd22b5d7fe CPU-Threads: 4; Betriebssystem:Windows 6.1; UI-Render: Standard; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-15_01:35:45 Gebietsschema: de-DE (de_DE); Calc: group and in Version: 6.0.0.0.alpha0+ Build ID: 9f3814af7264ce90685a82cbf4eb015a38f22bf7 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-06-28_00:47:42 Locale: de-DE (de_DE); Calc: group It is an import error.
The rose-rings image is placed inside of a textbox (so it gets placed in the foreground instead of the background during import). The 30-image is grouped with various shapes and bits. If anyone decides to waste their time with this one, also noticed that in LO the people have a transparent background (so that the rings show up behind them), while in MSWord the background is solid white.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Sushil Shinde, 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
reproduced in recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 3cb1ed4339fc9aec414c0f112a69705a7a4d9cc6 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Using "bring to front" on the People/30 image doesn't even bring it in front of the flower image. Note that the People/30 image isn't even listed in the Navigator.
(In reply to Stéphane Guillou (stragu) from comment #9) > Using "bring to front" on the People/30 image doesn't even bring it in front > of the flower image. That's because it's in the background. It needs to be brought to the foreground first. > Note that the People/30 image isn't even listed in the Navigator. Its parts are visible once it's ungrouped (as drawing shapes).
the flower (MC900412450[1].WMF) has a z-index:251661312 and the two people/30 image (MC900283119[1].WMF) has a higher z-index:251672576, both of which are positive numbers when placed in a sal_Int32. Likely the proper solution involves NOT letting the floating group shape go into the background? Why is it in the background anyway?
somewhere in between the 4.0.0 and 4.0.2 timeframe, the 30/couple object changed from being imported as an inline (as-character) thing to an in-the-background floating thing.
SimpleShape::createPictureObject looks like a good starting point to debug this.
This "hack a fix" patchset 1 works for this document, but I'm sure it will have bad side effects. I need to have it apply to a groupset only if not in header/footer (since in that case everything should be backgrounded).
https://gerrit.libreoffice.org/c/core/+/166345
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/00ef339bfc747897b8e4410fa0aa4397c4e45717 tdf#81956 vml import: put groupshape in foreground if positive z-index It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 67759 has been marked as a duplicate of this bug. ***
This still does not look exactly like in Word, but I think the similar bug 100037 covers the remaining issue, with Z-order of VML textbox (imported as TextFrame in Writer) and image.
Created attachment 193798 [details] Screenshot of the example file in Word 2016 and Writer master