Bug 134027 - [Editing] Anchored image move to wrong position when cells inserted above it
Summary: [Editing] Anchored image move to wrong position when cells inserted above it
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Calc-Images
  Show dependency treegraph
 
Reported: 2020-06-16 09:17 UTC by zzz
Modified: 2024-03-03 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
before (15.12 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-06-16 09:19 UTC, zzz
Details
after (15.15 KB, application/vnd.oasis.opendocument.spreadsheet)
2020-06-16 09:19 UTC, zzz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zzz 2020-06-16 09:17:38 UTC
Description:
Symptom:
For images pasted onto a cell and anchor mode set to "Anchor to Cell",
when you insert cells above that cell, sometimes the shifting distance
of images are wrong.


Steps to Reproduce:
(1) Open sample file
  20200616AnchorPositionTest1.ods
(2) The image in the top is on cell B2
(3) Select cell range B1:5 by mouse drag
(4) Right click menu "Insert" | Shift cells down


Actual Results:
(5) Image on B2 is expected to move to B7,
  but it actually moves to B4
  All other images also act the same.
  Note that the text in cell B1 moves correctly to B6.
(6) If you undo and retry, the bug repeatidly reproduces 100%.
File 20200616AnchorPositionTest2.ods
is a snapshot of step (5).


Expected Results:
(5) Image on B2 is expected to shift down 5 cells, which means to move to B7.



Reproducible: Sometimes


User Profile Reset: No



Additional Info:
Occurring condition:
I couldn't figure out the exact condition. What I can say is,
(a) Once the object begin to behave correctly, the are always correct.
(b) But if you cut an object/objects and paste them to another cell,
   the symptom may start again.
Comment 1 zzz 2020-06-16 09:19:02 UTC
Created attachment 162034 [details]
before
Comment 2 zzz 2020-06-16 09:19:56 UTC
Created attachment 162035 [details]
after
Comment 3 Regina Henschel 2020-09-26 17:13:07 UTC
I see this error in Version: 7.1.0.0.alpha0+ (x64)
Build ID: 0f99330f33868594ad253656805918115823f59d
CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: Skia/Vulkan; VCL: win
Locale: de-DE (en_US); UI: en-US
Calc: CL
Comment 4 QA Administrators 2024-03-03 03:15:05 UTC
Dear zzz,

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