When the mouse pointer is moved into a form field with associated Help Text, a hint is displayed for about 4 or 5 seconds then disappears. This is as I would expect. If, while the hint is displayed, the mouse pointer is moved out of the relevant form field to an area that is not associated with a field, or, worse, into another form field that does not have associated Help Text, the hint either remains on display until the timeout expires or, worse, is redisplayed in a slightly different position and the timeout seems to be restarted. This can be very confusing to a novice user - I would expect the hint to be cleared as soon as the mouse pointer moves out of the relevant form field. I was unsure whether to report this as a bug or as a request for an enhancement, but it seems to me to be just about important enough to be a bug.
I can not reproduce with LO 4.4.3, win7. Please could you attach test file? Thank you
Created attachment 116422 [details] LibreOffice BASE database file to illustrate the reported symptoms Open the attached odb file and display form Form1. Position the mouse pointer at the left-hand end of the active area of field Text2, which has associated HelpText configured - a box containing "Help" will appear immediately below the mouse pointer. Within a few seconds, while "Help" is displayed, move the mouse pointer diagonally up and right into the active area of field Text1, which does not have associated HelpText configured - the box containing "Help" clears then is immediately re-displayed slightly up and right from its original position. I am using LO 4.4.3.2 on Windows 7 Professional 64-bit.
I can confirm with Version: 5.1.0.0.alpha1+ Build ID: eb8c323d94bf13d4a373f88c6b932a97701c283b TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-06-05_00:59:00
Still present in LibreOffice 5.1.1.3
Still present lin LibreOffice 5.1.3.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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Still present in LibreOffice 5.4.1 (Windows 10 Home Premium 64bit)
** 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
Tested with LibreOffice 3.3.0. Exactly the same symptoms as described in the original bug report are exhibited using 3.3.0, so set version to "Inherited from OOo"
This bug seems to no longer be present in LibreOffice Version: 6.1.2.1 (x64) Build ID: 65905a128db06ba48db947242809d14d3f9a93fe CPU threads: 4; OS: Windows 10.0; UI render: GL; Locale: en-GB (en_GB); Calc: CL
I think it must have been fixed by changes for tdf#112356, which I think were implemented by Adolfo Jayme Barrientos - Many thanks