Bug 47120 - : Repeat Search keyboard shortcut doesn't work while focus is in Find toolbar
Summary: : Repeat Search keyboard shortcut doesn't work while focus is in Find toolbar
Status: RESOLVED DUPLICATE of bug 45903
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-08 18:31 UTC by skierpage
Modified: 2012-05-31 01:47 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skierpage 2012-03-08 18:31:07 UTC
Problem description: 
After performing a Find, the Repeat Search (default Ctrl+Shift+F) shortcut doesn't work until the focus leaves the Find toolbar.

Steps to reproduce:
1. In Calc and Word (haven't tried the others), press Ctrl-F.
2. Enter a word that occurs multiple times in the document and press Enter.
3. Scroll around, zoom, etc.
4. Press Ctrl+Shift+F to Repeat Search.

Current behavior:
So long as the keyboard focus remains in the Find toolbar, the Repeat Search keyboard shortcut does nothing. (Perhaps the Ctrl+Shift+F is not propagated to the main window's shortcut handling?) The workaround is to click in the main window, or realize the keyboard focus is still in the Find toolbar, and continue to press Enter.

It seems other LO keyboard shortcuts don't work if the keyboard focus is in the Find toolbar, e.g. F7 doesn't immediately pop up  Spelling (if I repeatedly press F6-F7-F6-F7 the dialog eventually pops up)

Expected behavior:
In every other program I use that has a find bar, the Find Next keyboard shortcut works regardless of the keyboard focus.
Platform (if different from the browser): 
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120216 Firefox/11.0 SeaMonkey/2.8
Comment 1 sasha.libreoffice 2012-05-31 01:47:24 UTC
Windows/Linux (non MacOS) bug

*** This bug has been marked as a duplicate of bug 45903 ***