https://bugs.documentfoundation.org/show_bug.cgi?id=165773
Buovjaga <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|24.8.5.2 release |7.1.0.3 release Status|UNCONFIRMED |NEW Keywords| |bibisected, regression Ever confirmed|0 |1 CC| |ilmari.lauhakangas@libreoff | |ice.org Summary|Check Boxes are getting |The checked state of Check |Un-Checked - or they appear |Boxes is getting changed |to be |just by scrolling (steps in | |comment 8) OS|Windows (All) |All --- Comment #8 from Buovjaga <[email protected]> --- (In reply to Mark from comment #7) > I am now using that exact version on my Windows 11 Pro 24H2 system > > Version: 25.2.1.2 (X86_64) / LibreOffice Community > Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 > CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 26100); UI render: > Skia/Raster; VCL: win > Locale: en-US (en_US); UI: en-US > Calc: CL threaded > > With the calc (.ods) file I provided, I can easily reproduce the problem. > > Just now I did this: > 1- entered text in a few random fields > 2- saved > 3- clicked ctrl-z until the changes were all undone > 4- saved > 5- noticed that a few checkboxes LOOKED un-checked > 6- scrolled down, then back up > 7- saw that those checkboxes still LOOKED unchecked > 8- clicked one of them, it still LOOKED un-checked > 9- clicked it again, and it LOOKED checked > 10- This makes me believe they only LOOKED un-checked at both (5) and (7) > > Simply SCROLLING down, then back up can make checkboxes LOOK un-checked. > > Sometimes they even LOOK un-checked when I first open the file. Simpler steps: 1. Open attachment 199840 2. Scroll down, pay attention to A32 and A34, scroll past them so they go off-viewport 3. Scroll back up You might have to scroll back and forth twice, but in the end A32 and A34 will have turned from checked to unchecked. This started some time in 7.1, but unfortunately the history is a bit messy. Linux is plagued by some icon change issues and while on Windows it was a bit better, but with win64-7.1 I got a bibisect commit that was a range of commits. I will attach a log of the commits and their messages. Inspecting the range with: git log --stat --pretty=short --graph b5cb211f80fd87c109633232cf340ac7969c8648...1aa9a2ac5341d457bbdc00b987285203d11333f1 | grep -B 10 -A 10 --color=always " sc/" | less -R I don't know what it might be. Somehow vaguely suspicious is a97539174fd7f76713291dd4e8138adb1f776c91 delay and batch calls to StartListeningFormulaCells() (tdf#133302) -- You are receiving this mail because: You are the assignee for the bug.
