Description: After a column is inserted that would affect the cell address of conditional formatting, the conditional formatting list dialog still reports the pre-insertion address for formatted range. Behavior is consistent for first action of insertion, and is self-correcting on document save/load cycle. Steps to Reproduce: 1.Create a conditional format for a cell in, say, column C 2.Right click column B header and select Insert Column 3.Click Format>Conditional>Manage Actual Results: Although the conditionally formatted cell is now in column D, the conditional format dialog (and the edit dialog) still shows column C. When the entry is clicked the blue marking border shows on column C in the document, although formatting continues to work correct on what is now column D Expected Results: The conditional format dialog should indicate column D, and when the format entry is clicked Calc should outline column D cell(s), the cell(s) that are actually now conditionally formatted Reproducible: Always User Profile Reset: No Additional Info: Bug may be spurious, but appears to be 100% of time when a conditional formatting is first added to a document and a column before the formatted cells is inserted. If this behavior is consistent, then bibisecting results in: 8a8df9a34bf44514ec1fe53ff85b3d43216ab75a is the first bad commit commit 8a8df9a34bf44514ec1fe53ff85b3d43216ab75a (HEAD) Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat May 11 18:41:47 2024 -0700 source 387a9c445793e8377f85e508d935dc070fd8ab74 source 387a9c445793e8377f85e508d935dc070fd8ab74 instdir/program/sclo.dll | Bin 17332736 -> 17332736 bytes instdir/program/setup.ini | 2 +- instdir/program/version.ini | 2 +- 3 files changed, 2 insertions(+), 2 deletions(-)
Created attachment 197038 [details] Example file where problem occurred This is an example of a file in which the problem occurred with the failure of the conditional formatting dialog to reflect the new location of conditionally formatted cells after the insertion of a column to the left. The document includes screen shots that represent the error.
Works fine with Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8a6919f39b4b871904a2a4199755ca619aa707e2 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Reproducible Version: 24.8.2.1 (X86_64) / LibreOffice Community Build ID: 0f794b6e29741098670a3b95d60478a65d05ef13 CPU threads: 16; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded So seems it was fixed in master.
I concur with m_a_riosv. I can reproduce in Version: 24.8.0.3 (X86_64) / LibreOffice Community Build ID: 0bdf1299c94fe897b119f97f3c613e9dca6be583 CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded and it doesn't happen in Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 54a836fa5af3428d893cffe5d7a0963b092e9f70 CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 22631); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Thanks for the bibisect. Based on the blamed commit and the fixing ones, I guess it's bug 160252 (bug 162692 was also covered by the fix that is only in 25.2). *** This bug has been marked as a duplicate of bug 160252 ***