when the mouse pointer passes over a cell containing a comment track of the upper part of the comment is displayed in the table! you must click to remove these residues. very unpleasant
please provide a test file and a screenshot of what you consider a bug. P.S. edited summary notes.
Created attachment 85820 [details] attachment-9770-0.html Hello, please find attached a file with which I am having problems posting. Your comment my bug is not really accurate: in fact only *_résiduts_* comments are displayed *_AFTER_* the mouse is passed over the cells containing a comment. Thank you for your help. Francois (I tried to print as pdf spreadsheet with residues comments but when it displays the pdf résiduts not appear?) Le 13/09/2013 05:10, bugzilla-daemon@freedesktop.org a écrit : > tommy27 <mailto:barta@quipo.it> changed bug 68784 > <https://bugs.freedesktop.org/show_bug.cgi?id=68784> > What Removed Added > CC barta@quipo.it > Summary livre office calc version 4.0.5.2 comment displayed in the > table when mouse pointer passes over > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=68784#c1> > on bug 68784 <https://bugs.freedesktop.org/show_bug.cgi?id=68784> from > tommy27 <mailto:barta@quipo.it> * > please provide a test file and a screenshot of what you consider a bug. > > P.S. edited summary notes. > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You are on the CC list for the bug. > * You reported the bug. >
Created attachment 85821 [details] attachment-9770-1.dat
Created attachment 85822 [details] test.ods
(In reply to comment #2) > Hello, > please find attached a file with which I am having problems posting. I tested the file with 4.0.5.2 and 4.1.1.2 under Win7 64 but I do not see issue with it. mouse passes over cells with comments, comments show up then disappear when moving to another cell. this is how the feature is intended to work. > Your comment my bug is not really accurate: in fact only *_résiduts_* > comments are displayed *_AFTER_* the mouse is passed over the cells > containing a comment. Thank you for your help. > Francois please translate *_résiduts_* in English since I do not understand French maybe do you mean that the comment pop-up doesn't go away unless you click on it? > (I tried to print as pdf spreadsheet with residues comments but when it > displays the pdf résiduts not appear?) > try posting a screenshot with any screencapture software. I don understand exactly which problem you are describing.
Hello résiduts means that after the cursor moves to the cell containing a comment yellow thick line remains on the columns C D and sometimes E. If I left click near these lines, they disappear one by one. francois. Le 14/09/2013 12:29, bugzilla-daemon@freedesktop.org a écrit : > > *Comment # 5 <https://bugs.freedesktop.org/show_bug.cgi?id=68784#c5> > on bug 68784 <https://bugs.freedesktop.org/show_bug.cgi?id=68784> from > tommy27 <mailto:barta@quipo.it> * > (In reply tocomment #2 <show_bug.cgi?id=68784#c2>) > > Hello, > > please find attached a file with which I am having problems posting. > > I tested the file with 4.0.5.2 and 4.1.1.2 under Win7 64 but I do not see issue > with it. mouse passes over cells with comments, comments show up then disappear > when moving to another cell. this is how the feature is intended to work. > > > Your comment my bug is not really accurate: in fact only *_résiduts_* > > comments are displayed *_AFTER_* the mouse is passed over the cells > > containing a comment. Thank you for your help. > > Francois > > please translate *_résiduts_* in English since I do not understand French > maybe do you mean that the comment pop-up doesn't go away unless you click on > it? > > > (I tried to print as pdf spreadsheet with residues comments but when it > > displays the pdf résiduts not appear?) > > > > try posting a screenshot with any screencapture software. > I don understand exactly which problem you are describing. > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You are on the CC list for the bug. > * You reported the bug. >
Created attachment 85824 [details] bug screenshot Ok, now I understand and I reproduce the bug. as you may see in the attached screenshot when comment pop-up disappears, a small part of its upper border still remain visbile.
set status to NEW and edited summary.
** 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 on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
2015/04/01 Hello, Now : Version: libre office 4.4.0.3 Build ID: de093506bcdc5fafd9023ee680b8c60e3e0645d7 Locale : fr_FR hardware : x86-64 (AMD64) software : Windows 8.1 professionnel And...... Dommange is that this problem is still present Thank you for your help. Francois
** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
hello, the bug is still present current version : 5.0.5.2 hardware : x64 (amd64) software : windows 10 professionnel Thank you for your help. Francois
affects LibO 5.2.0.0.alpha0+ too Build ID: d6bf3bcd8b51012d55a2ec962800a8549e2b85e1 CPU Threads: 4; OS Version: Windows 6.2; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-04-15_06:46:09 Locale: it-IT (it_IT) the bugs happens regardless if OpenGL is on/off
My dad runs LibreOffice 5.2.2.2 on Windows 10 and is experiencing this issue as well. When he hovers the mouse over a cell with a comment, the comment will appear. When he moves the mouse outside of the cell, the comment remains displayed. If he happens to hover over more than one cell with a comment, the comments of all the cells appear and he can't make them disappear (outside of closing the spreadsheet).
I almost forgot. My dad's runing LibreOffice Calc 5.2.2.2 on Windows 10.
bug still present under Win8.1 x64 using LibO 5.4.0.0.alpha0+ Build ID: 9cfb2f2f03b5ec086487fd483298466db0b09010 CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-20_23:58:02 Locale: it-IT (it_IT); Calc: group
bug not present in LibO 3.6.7.2 hence it's a 4.0.x regression needs bibisecting
On Saturday, April 29, 2017, I upgraded my dad's Windows 10 system to the 64-bit version of LibreOffice 5.3.2. The comments didn't linger as I previously reported with the 32-bit version of LibreOffice 5.2.2 that was installed on his system.
I confirm is still reproducible under Win7 x64 using the 32-bit version of LibO 5.3.2.2
** 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
Hello, Now Version: 5.4.6.2 (x64) Build ID: 4014ce260a04f1026ba855d3b8d91541c224eab8 Windows 10 1803 with this version the bug is still present but less visible. a very small part of upper border still remain visbile. thanks you for your help. Cordially François
I'm not seeing the problem anymore. Could you test with a master build? If it still happens, you could attach a new screenshot. https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/current/ Version: 6.1.0.0.alpha1+ (x64) Build ID: 8c07193cec5e09d50b20bc5b107da02a7d8f05a5 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-05-17_23:03:56 Locale: fi-FI (fi_FI); Calc: group
Hello, i have installed master build 6.1. i have captured a screenshot. a very small part of upper border still remain visbile. thanks you for your help. Cordially François
Created attachment 142207 [details] scrennshot Hello, i have installed master build 6.1. i have captured a screenshot. a very small part of upper border still remain visbile. thanks you for your help. Cordially François
I do reproduce this with latest master on Linux (gtk3). Note: the comment trace is a multigenerational issue. Already in the oldest commit of Linux 43all repo (3.5.0), the comments leave a very faint horizontal line that you almost do not notice. At some point, the boxes also leave a vertical trace. Then, surprisingly, there was a moment in 4.1.0.0alpha0+ commits where no traces were left at all (this is before the problem in this report appeared). I bibisected marking "bad" the builds which showed the black horizontal line. The range given was https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=fff4d120866a0be3cd8185f2c67bb9f59b1a6a3f...fd84daf696a368c2c7561b5253b32a63ecdeca4a I do not notice anything immediately suspicious in the range.
don't repro in Version: 6.3.0.0.alpha0+ Build ID: 3083fe569f96bf0289da1e9d0ef7da15ab22e2f6 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-04-16_01:39:55 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded Status WFM
Was last reproduced in master on Linux (gtk3). Cannot confirmed "fixed" with Windows.
I'm not seeing the residues anymore. On the other hand, new interesting issues have come up. I will report them after further testing with newest builds. 1. On Linux, most of the comments display only partly or not at all 2. On both Win & Linux, View - Comments causes a crash Arch Linux 64-bit Version: 6.3.0.0.alpha0+ Build ID: 9030ffb1a1b282eb2c6d1773930b0de0d42df447 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 13 April 2019
(In reply to Buovjaga from comment #28) > I'm not seeing the residues anymore. On the other hand, new interesting > issues have come up. I will report them after further testing with newest > builds. > > 1. On Linux, most of the comments display only partly or not at all This is bug 120797 > 2. On both Win & Linux, View - Comments causes a crash Reported as bug 124778
Comments are behaving correctly for me in Calc 6.1.5.2 on Ubuntu 18.10 and in Calc 6.2.2.2 on Windows 7 (32-bit).