If the anchoring of a form control that was resized to fit the cell is set "to cell" from the Control Properties dialog, it moves to another cell toward the top left. Steps: 1. Open Calc (or open attachment and jump to step 6) 2. Insert > Form Control > Text box 3. Trace the control further than column C and row 2 (for example, on cell E10) 4. right-click on the control > Anchor > To cell (or "resize with cell", same thing) 5. right-click on the control > Fit to cell size 6. right-click on the control > Control properties > Anchor > To cell (repeatedly) Result: the control jumps from cell to cell at each click, until it settles in cell C2. The change can't be undone. Same happens with other controls, e.g. a Numerical Field. Note that the setting does not have the option "To cell (resize with cell)", which might be related to the issue? Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Also reproduced with sample file in Ooo 3.3, so issue is inherited (although the option to "Fit to Cell Size" was only added in 6.1 for bug 116108). Seems to have to do with the position of the top-right corner, possibly because of rounding. Samuel, I thought you might be interested?
Created attachment 191307 [details] sample ODS with text box form control anchored to cell, resized to fit cell
Reproducible Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded
Dear Stéphane Guillou (stragu), 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