Description: Anchor still visible after deselecting image Steps to Reproduce: 1. Open the attached file 2. Select the image on the first page 3. Scroll to the second page and click inside the text -> Anchor still shows Actual Results: Anchor still visible Expected Results: Should hide Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 159723 [details] Example file
Can't confirm with Version: 7.0.0.0.alpha0+ (x64) Build ID: 1c9ced04189c9d23ffea05d5570960b54b05ef28 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB Calc: CL
Created attachment 159758 [details] Screencast
Bibisected with Linux 50max, but the result seems weird: https://git.libreoffice.org/core/+/fd68059586246f415a5fa6637fafad1ac9293e92%5E!/ tdf#81475 added/removed/rearranged buttons from various toolbars I did double-check with the bad vs. good commit. I hope someone can confirm.
The image is anchored to character, the anchor shouldn't be displayed somewhere outside the document area. I'd call that the primary bug, and it's been there since 3.3.0. Bug 99932 is a bit similar. A note on the originally described issue, at first I could confirm the commit Buovjaga found in comment 4 (which obviously can't be the real culprit), but after switching to single-page view, and repeating the same steps, it's buggy even in 3.3.0. Considering the anchor is in a buggy position, I don't think this is worth pursuing, and suggest to focus on the anchor positioning itself.
Dear Telesto, 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