Steps to reproduce: 1. Create new spreadsheet 2. Select entire row (for example row 2 in Sheet1) and set background color of the row (for example yellow) 3. Add new sheet (Sheet2) 4. In Sheet2 enter formula reference to Sheet1, for example set A1=Sheet1.A1 5. Now select entire row 1 in Sheet2 and delete this row (i.e. cell A1 containing the reference will also be deleted) 6. Switch to Sheet1 and see result - yellow background is left only for A2 and for columns starting with B it has moved to row 1, while it is expected that row 2 keeps yellow background...
Repro in LO 7.6.5.2 but not in LO 7.5 on MS Windows > Regression.
NO repro with Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6d5d9eaa61505cebaf3bde4bfc157d8e19fec8de CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo Please, can you test with dev version? http://dev-builds.libreoffice.org/daily/master/ Thank you
I can still reproduce with dev version Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 658a212585c56540a17c41111e6829716d4ef4e3 CPU threads: 4; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
(In reply to pavelz from comment #3) > I can still reproduce with dev version Also on: Version: 24.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 658a212585c56540a17c41111e6829716d4ef4e3 CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded
Reproducible with VCLPLUGIN = gen This seems to have begun at the below commit in bibisect repository/OS XXXX. Adding Cc: to László Németh ; Could you possibly take a look at this one? Thanks 48d095549a2c5b45882c8a7f30d30f2bf1ad30fa is the first bad commit commit 48d095549a2c5b45882c8a7f30d30f2bf1ad30fa Author: Jenkins Build User <tdf@pollux.tdf> Date: Mon Oct 30 14:20:44 2023 +0100 source c37e74949cf3cd11b701e4aea943aba4e8c1d4f8 152814: tdf#153437 sc: fix broken formatting without performance regression | https://gerrit.libreoffice.org/c/core/+/152814
IMHO, this is not just a "normal" bug, as it can generate DATA LOSS, without the user even being aware of such.
(In reply to ady from comment #6) > IMHO, this is not just a "normal" bug, as it can generate DATA LOSS, without > the user even being aware of such. Well, perhaps "Data Loss" is not the most adequate term in this case, but at least "formatting lost".