Created attachment 172877 [details] Document to use as start for reproducing the bug Open attached document in Word, to see that it has a shape with effect 'Reflection'. Close. Open document in LibreOffice Daily. Select the shape and add a shadow: Direction Top, 0.5" distance, Color Black, 4pt Blur, 60% Transparency. Other shadow settings produce the error too, but so the shadow is good visible. Save the document as new docx document. Open the saved document in LibreOffice or Word. Error: There is not shadow. Expected: Shadow exists. The problem is in method DrawingML::WriteShapeEffects in oox/source/export/drawingml.cxx. If aEffects.hasElements() is true - which is the case here, because it contains the effect 'Reflection', then the flow goes to 'else'. There it starts immediately with a loop over aOuterShdwProps. But that is empty, because the InteropGrabBag does not have a shadow, but shadow was newly set in LibreOffice. How to export an own shadow can be seen in #4243-#4266. It is an error in the flow logic.
Moving to NEW
Hello Regina, Thank you for reporting the bug. I cannot see any reflection effect on the moon in Microsoft Word or LibreOffice Writer. Could you confirm this is a good document to use to reproduce the bug, please? Best regards
In the chat, Sophie told me she used Word 2007, which is apparently too old to render the reflection. I see the reflection in office.com I reproduce the disappearing shadow. Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: a389e6bd7aacfa4e1ff1ea3a46199fb381d1131f CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 10 July 2023
Dear Regina Henschel, 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
The error still exists as described in Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 697fadb8f4efdc09091088261ca1b43984c029b4 CPU threads: 32; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded