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
Could not reproduce on OS X with LO 5.1 nightly. Setting to NEEDINFO. Does this persist with the latest nightly build? http://dev-builds.libreoffice.org/daily/master/ After providing the requested info, please reset this bug to UNCONFIRMED (should it be persisting) or WORKSFORME (should it be solved with a newer LO version).
@steve it's a Windows only bug
Yep, would be great to have it retested.
retested under Win8.1x64 bug still present in LibO 5.1.0.0.alpha1+ Build ID: df7595a5f5871f8343e4ee3869ad153e3ae4a7f3 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-25_14:29:31 Locale: en-US (it_IT) adding bibisectRequest in the whiteboard the issue started in 3.6.x see comment 8
opppsss... sorry I forgot that Windows only bugs are not bibisectable...
This also reproduces in Linux. See bug 73287.
Adding keyword 'preBisect' as this regression was introduced before branch 4.4 and therefore it can't be bibisected as there's no bibisect repository for this branch.
any progress about this? Still present in LO 5.4.2
*** Bug 113297 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still rero for xls from attach in Version: 6.2.0.0.alpha1+ (x64) Build ID: 0b2d153f58c83fb289c96b348631e44e553b1a9a CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2018-11-02_21:11:48 Locale: ru-RU (ru_RU); Calc: threaded but i can't repro it in ODS from attach
The issue seems to be less important in 6.2.0.3 (x86 - Windows 10) On my system, the shadow issue only affects the upper border (previously there were also some issue with the right border) When the shadow issue is visible, it is a very thin line now, much less visible than before. Finally, at some zoom level, there is no issue at all. (but I don't remember if it was already the case before) I've not been able to reproduce the issue with either of the 2 attached test-cases. If needed I can provide a new one with the effect described above.
I can't reproduce it on newer versions. Version: 7.2.0.0.alpha0+ (x64) Build ID: c0eee433e079d8e3413f4691607e075b99af92b0 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: cs-CZ (cs_CZ); UI: en-US Calc: threaded Can those who experience it test it on newest version? Download here: https://dev-builds.libreoffice.org/daily/master/ Maybe it's good to write info about OpenGL ... Info here: https://wiki.documentfoundation.org/OpenGL#Windows Mine OpenGL info is: Renderer: Intel(R) HD Graphics 3000 Vendor: Intel Version: 3.1.0 - Build 9.17.10.4459 Shading language version: 1.40 - Intel Build 9.17.10.4459
Dear Peter H. Rankin Hansen, 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