Description: When an image on a page is set to anchor to page, trying to interact with the anchor to change the page it is anchored to instead opens the header/footer, making it impossible to change the page these images are anchored to effectively. When switching to another anchor method, it is unpredictable where the image will end up, and has on multiple occasions become hidden and unable to be interacted with entirely. Steps to Reproduce: 1.place one or more images on a page 2.set anchor to page 3.try to move the anchor Actual Results: the image lost focus, and the header gained focus. Expected Results: allowed movement of the anchor to another page. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no
Repro with 7.1 and with 4.4.7.2 dragging they anchor with header enabled in multi-page view isn't working. However selecting the image as change & dragging is working perfectly fine & also copy/paste Is there specific reason for this to be actually 'needed'? Feels kind of trivial (even though being a bug). So tend to set priority that way... Usage of To page probably even more reduced now it's not in the context menu anymore
I'm entirely unable to drag the image off the page it's anchored to without changing the anchor mode. This isn't a huge issue with smaller images surrounded by text it can anchor itself to, but images or frames that fill more than one-third of a page become really cumbersome to move between pages visually. Cut/paste seems to work fine for full-page images. I guess I didn't expect it to maintain the anchor data... I thought I'd bumped the priority down, so if it was high or normal that's my bad. (In reply to Telesto from comment #1)
Dear stefan.m.terry, 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