Description: Attached user document was created in Word and contains some explanatory text boxes above an image that has custom Contrast and Recoloring settings in Word set. Opening the image in Writer causes the text boxes hide behind the image. Contrast and Recoloring settings cause the image to appear among the Drawing objects in the Navigator, but removing these settings causes the image appear as image, and the Z-order of the image and the shapes is correct. Steps to Reproduce: Steps to reproduce: 1. Open attached document in Writer, it should have a map of Hungary and two explanatory text boxes with county names in them 2. Observe that the image of the map hides the two text boxes, but they are visible in the Navigator under Drawing Objects 3. Right click on the image, and choose Arrange – Send to Back 4. The text boxes appear on top of the image, as they would in Word. Actual Results: The image hides the text boxes. Expected Results: The text boxes should appear on top of the image. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 152100 [details] Example file from Word
Created attachment 152101 [details] Screenshot of the original document side by side in Word and Writer
Created attachment 152102 [details] Screenshot of the cleaned document side by side in Word and Writer
Created attachment 152103 [details] Example file from Word without custom image settings
I confirm it with Version: 6.4.0.0.alpha0+ (x64) Build ID: b170256fb6ebaf774b02b89835b19d9f3a1afb89 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-07_03:30:35 Locale: de-DE (de_DE); UI-Language: en-US Calc: threaded
This is fixed by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=99847d6b3005c5444ed5a46ca578c0e40149d77c author Miklos Vajna <vmiklos@collabora.com> 2020-02-12 15:02:18 +0100 committer Miklos Vajna <vmiklos@collabora.com> 2020-02-12 21:34:28 +0100 DOCX import: fix ZOrder of inline vs anchored shapes Thanks Miklos for fixing this! *** This bug has been marked as a duplicate of bug 103271 ***