Description: Pasting an additional image with anchor to page set, will delete the first image (anchored to page) Steps to Reproduce: 1. Open the attached file 2. Select the red frame 3. CTRL+X 4. CTRL+V Actual Results: Ape disappears Expected Results: Should be present Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: <buildversion> CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: ru-RU (nl_NL); UI: en-US Calc: CL and in 3.5.0.3
Created attachment 163881 [details] Sample File
I confirm it with Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL But the problem is something different: 1. Open the attached file 2. Select the red frame 3. CTRL+X Result: Image37 is selected (and therefore it disappears after CTRL+V) So bug sumary should be something like "Image behind a frame is selected, if frame is cut off". Do you agree?
(In reply to Dieter from comment #2) > I confirm it with > > Version: 7.1.1.2 (x64) / LibreOffice Community > Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 > CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: > win > Locale: de-DE (de_DE); UI: en-GB > Calc: CL > > But the problem is something different: > 1. Open the attached file > 2. Select the red frame > 3. CTRL+X > > Result: Image37 is selected (and therefore it disappears after CTRL+V) > > So bug sumary should be something like "Image behind a frame is selected, if > frame is cut off". Do you agree?
Telesto, you've changed bug summary, so I think you agree => Status NEW
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
Still present in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ab20dba30769a5a52830220daa347772485db6a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded