When a cell comment has been shown because the red dot was "mouse-overed", not all cells the comment was overlapping are redrawn correctly, as part of the shadow (usually the bottom) for multi line comments may be left in place. This seems to happen only for overlapped cells BELOW the one which contains the comment. The problem has persisted for at least two years by now. At that time, it was most shadows, not just those below, so some improvement has been seen ;o)
Could you please provide a screenshot of this error?
Created attachment 88561 [details] The comment shown
Created attachment 88562 [details] The comment shadow after moving the mouse away
Created attachment 88563 [details] Navigating into the shadow This should illustrate the shadow error quite well.
Done. Good hunting ;o)
would you please attach a test .ods file where you can reproduce this issue?
I've sent the file privately
Created attachment 94157 [details] test case removed sensible informations from the file you sent me privately. bug is reproducible from LibO 3.6.0 to 4.3alpha not reproducible in LibO 3.5.7, hence regression of the 3.6.x branch
set status NEW. updated version field. added regression keyword. added Calc expert to CC list.
Same problem exist in 4.2.0.4 and 4.3.0.0Beta1 New screenshot attached
Created attachment 99674 [details] Another Testcase
Created attachment 99675 [details] Another screenshot
Moreover, I have made some test on Ubuntu (14.04 in a WM) and on Windows 7 64 bits with the *same* file. The issue only occured on Windows.
Version 4.2.5.2 is even worse. If I mouse over the red dot for a comment, the entire comment and it's arrow will be left on screen, until you navigate into the cells it covers - and then only the relevant cell will be redrawn, leaving the rest of the comment visible. Scrolling the page will remove the comments. I have a partial screendump with four visible comments.
Created attachment 101977 [details] Screendump for comment 14, comments left visible
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.