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.
My comment 1 and comment 3 regards the UNO assignment were off topic. For legacy Find use, the F3 key is hardcoded (as Key_F3) assigned at tbunosearchcontrollers.cxx#301 to activate the Find bar, so non-customizable. <F3> and <Shift><F3> Find next and find previous movements are held over from legacy MS Word handling (since removed IIUC), but they remain in common use, e.g. for Notepad and the Visual Basic Editor as well as new Visual Studio Code for Find Next and Find Previous. However, case can be made as in OP that behavior seems wrong. But not the assignment of the <F3>, but that its behavior changes depending on *edit cursor* focus. When the Find bar tb has edit cursor focus, the <F3/Shift+F3> pair perform the next/previous Find actions. But with Find tb open, but edit cursor shifted onto canvas, the text at cursor position becomes the new search target and throws an info warning 'AutoText for shortcut <selected text> not found'. And when UI is not focused to document canvas (e.g. is on Main menu or Std Toolbar)--the F3 pair then have no action. Likewise get the same behavior when edit cursor is not on the Find bar affecting the <Ctrl>+G/<Shift><Ctrl>+G Find next/previous shortcuts. Except that the <Ctrl>+G is now assigned and when on document canvas now launches the GoTo page dialog. A this point, I don't think removing the <F3> pair would be correct, it is not a bug. They are valid common shortcut. But maybe should be bound to the Find bar being open even if unfocused, and the Find next/previous not dependent on edit cursor and UI focus placement? As in OP "... it should work even when cursor is not inside search box."
(In reply to V Stuart Foote from comment #11) >... But with Find tb open, but edit cursor > shifted onto canvas, the text at cursor position becomes the new search > target and throws an info warning 'AutoText for shortcut <selected text> not > found'. And that looks to be a collision with the AutoText feature in Writer for the .uno:ExpandGlossary 'Run Auto Text Entry'. Hmm, I'd imagine the F3 as Find Next really does need to be bound to focus of the Find bar as is, and this becomes a Wont fix.
There might be conflicts but I see no good reason for hard-coded shortcuts.
(In reply to Heiko Tietze from comment #13) > There might be conflicts but I see no good reason for hard-coded shortcuts. You mean liike <F6> and <F10>? ;-) Or even <F1>, <Ctrl>+W, <Ctrl>+Q, <Ctrl>+C, <Ctrl>+V, <Ctrl>+X, <Ctrl>+F, <Ctrl>+H, and etc. [1] Hard-coded are user expectations, warts and all including headache(s) of localization(s). =-ref-= [1] https://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts#Text_editing
(In reply to V Stuart Foote from comment #3) > 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; officecfg/registry/data/org/openoffice/Office/Accelerators.xcu <node oor:name="F_SHIFT_MOD1" oor:op="replace"> <prop oor:name="Command"> <value xml:lang="x-no-translate">L10N SHORTCUTS - NO TRANSLATE</value> <value xml:lang="en-US" install:module="unxwnt">.uno:RepeatSearch</value> </prop> </node> <node oor:name="G_MOD1" oor:op="replace"> <prop oor:name="Command"> <value xml:lang="x-no-translate">L10N SHORTCUTS - NO TRANSLATE</value> <value xml:lang="en-US">.uno:RepeatSearch</value> <value xml:lang="es">.uno:Save</value> </prop> </node> </node>
(In reply to Heiko Tietze from comment #13) > I see no good reason for hard-coded shortcuts. I currently see excellent reasons for hard coded shortcuts. - .uno:RepeatSearch (Ctrl-Shift-F) currently doesn't work when in the quick find. - F3 is practically a Windows/Linux standard for Find Next (MS Word being a notable exception). - Ctrl-G is a Mac and Linux/Gnome standard for Find Next (I documented this a bit more in bug 70001.) So utilising the user's muscle memory is an excellent accomplishment in quick find. (In reply to V Stuart Foote from comment #3) > On Windows builds that is already <Ctrl>+G by default That should say 'On Mac builds ...'. For Unix/Windows it is Ctrl-Shift-F AFAICS. I agree with Comment 12: WONTFIX - except to have .uno:RepeatSearch ALSO work in the quick find (as well as implementing bug 47122). I could also imagine adding hardcoded Shift-F4 and Ctrl-Alt-Y (the MS Word shortcuts for Find Again). Apparently MS Word also has a BrowseNext (Ctrl-PageDown) and BrowsePrev (Ctrl-PageUp). Those would also make good sense.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/25ff7de2f7dc9557366954482c9d735a7e9a6f7e tdf#102307 quick find: also use .uno:RepeatSearch to find next It will be available in 27.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/6e873ec987caeb78086c55607540971a4f9c9141 tdf#102307 quick find: add hard-coded MS Word keyboard shortcuts It will be available in 27.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/3552e250f442f4b7da207233faf8e7b8bdbcf049 tdf#102307 quick find: add hard coded keyboard shortcut to label It will be available in 27.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.