Description: I'm not really positive what causes the double arrow lines to not work but most of the time when I drag a new jpg/jpeg picture in that is an update of the same previous picture the arrows have a tendency of staying hidden behind the picture when they were intended to be on top of the picture and visible. You can mitigate this by copying and pasting the arrow again in a different location, using that one instead of the affected arrow line. Thes Pictures were created with Apeaksoft Screenrecorder on Windows 10/ Intel 64 bit system. I'm using Libre Office Calc. Steps to Reproduce: 1. Delete previous bad picture 2. Copy or drag the replacement picture from the folder location of the picture to Libre Office Calc 3. I Hope the double Arrow line doesn't get stuck behind the picture. 4. If it is copying bad double arrow line create a new one. 5. Use the newer unaffected double arrow line instead Actual Results: The new picture hides the arrows that previously were on top of it. Expected Results: I would think dragging in the new picture would still let the arrows be on top instead of hidden. Reproducible: Sometimes User Profile Reset: No Additional Info: None
Please attach an example document. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 186507 [details] It is a map of the Wilderness area of a NWN Server I play on. The issues are with the Wilderness Map.
[Automated Action] NeedInfo-To-Unconfirmed
Hello [Jeffry], Thank you for reporting the bug. I can confirm that the bug is present in master. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d9031bd83ffe718a80da9ecbdbeb485e35fbabee CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Dear Jeffry, 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