https://bugs.documentfoundation.org/show_bug.cgi?id=47122
--- Comment #10 from Hossein <[email protected]> --- Bug tdf#142219 also provides some good points: the problem is "inconsistency" in find-next and find-backward shortcuts. > Ultimately this report is asking for another shortcut that: > -reverses the search direction > -does the FN_REPEAT_SEARCH > -reverses the search direction again > > That would allows the same keyboard shortcut to continue searching in the > reverse direction. So perhaps FN_REPEAT_REVERSE_SEARCH This might be doable, but it is doubling down on a path that is even now confusing. Also, it does not match the user's expectation, as they described. See below: > Expected behavior: > I think it would be better if LO worked more like other applications and had > Find Next / Find Previous commands matching the toolbar. (Maybe having > separate > commands would permit LO to have Find Next / Find Previous items in its Edit > > menu, like KDE programs and Firefox; I guess that's another bug...) This is the expected behavior, having two shortcuts for forward and reverse search. I think we can make it happen. One issue that I see is the collision with Ctrl+G for "Edit > Go to Page". This is also happening for F3, for "Run AutoText Entry". IMO, re-using shortcuts in this way is a bad idea. Ctrl+shift+F has its own issues: it does not work when the find toolbar is open. We should either change that behavior, and make some of these shortcuts exclusive to find next / find previous, or otherwise, it would be hard (if not impossible) to address the issue of confusing and conflicting shortcuts. > Bug 70001 indicates that the Ctrl-F find toolbar has some (secret) hard-coded > keyboard shortcuts. F3 and Ctrl-G for Find Next, while Shift-F3 and > Shift-Ctrl-G > do Find Previous. Lack of ability to configure the search shortcuts is another issue. -- You are receiving this mail because: You are the assignee for the bug.
