1. Open Calc or Writer 2. Ctrl + F to open quick search toolbar and activate 3. Search something, end with Enter 4. Press F3 to find next 5. Click inside document 6. Press F3 to find again. No boom. Either nothing happens or F3 has another use now. I think whatever shortcut we use (F3 and Ctrl+G are generally common ones), it should work even when cursor is not inside search box.
F3 is undefined--both Globally and in Calc--it has no Find function in LibreOffice. And, <Ctrl>+G *is* the defined shortcut for "Repeat Search" and functions from the Find toolbar (<Ctrl>+F) and the Find & Replace dialog (<Ctrl>+H) You can of course customize your Keyboard to assign F3 to Repeat Search if you prefer--but we wont make it a default assignment as that would duplicate the <Ctrl>+G already used.
Put cursor back to search box and F3 will work (until your cursor is there). That's the problem.
As mentioned the behavior you seek is *already* provided with a customizable short cut assigned to the "Repeat Search" action--i.e. .uno:RepeatSearch. On Windows builds that is already <Ctrl>+G by default, and on RPM builds it is to <Ctrl>+<Shift>+F; simply set the shortcut you prefer from Tools -> Customize -> Keyboard: Edit Functions, "Repeat Search" F3 is *not* assigned to a LibreOffice search related shortcut action in any module, nor used in LibreOffice globally for an action. It has some specific uses--notably in Calc to move between errors, and in Draw/Impress to enter a group of objects. The behavior of the F3 key executing find--e.g. .uno:RepeatSearch--while in the FindBar with cursor focus in the TextFind widget is anomalous in that it is not assigned as a shortcut, but is being parsed in the source code of the widget. This anomoly is present in both Windows and Linux builds and affects Writer and Calc. Adjusting summary for that issue.
I think whatever happens should be consistent. So I vote for removal of F3 doing anything in this context.
** 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
It still happens in 6.2.2.2 svx/source/tbxctrls/tbunosearchcontrollers.cxx@269 // Execute the search when Return, Ctrl-G or F3 pressed if ( KEY_RETURN == nCode || (bMod1 && (KEY_G == nCode)) || (KEY_F3 == nCode) ) should be: // Execute the search when Return or Ctrl-G is pressed if ( KEY_RETURN == nCode || (bMod1 && (KEY_G == nCode)) )
Dear mahfiaz, 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://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
Dear mahfiaz, 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
The bug is still there in 7.5.2.2. The patch is in my previous comment.