Bug 129281 - Find and Replace dialog: Replace shortcut (r) doesn't work; and no repeater function
Summary: Find and Replace dialog: Replace shortcut (r) doesn't work; and no repeater f...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Find&Replace-Dialog
  Show dependency treegraph
 
Reported: 2019-12-08 20:40 UTC by R. Green
Modified: 2019-12-10 07:37 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 R. Green 2019-12-08 20:40:08 UTC
Use any convenient writer document as a specimen.

1. Position the cursor at the beginning of the text.
2. Open the Find and Replace dialog (Ctrl + H)
3. Put a letter, say, into the Find box. Add some asterisks, say, in the Replace box.
3. Click the find shortcut (x) to select the desired letter.
4. Click the Replace shortcut(r).

Expected result: The selected letter is replaced and the cursor selects the next occurence of the letter.
Actual result: The focus shifts to the "Replace" key but nothing further happens.

Workaround: The user has to click the Replace key with a mouse instead.

Note: The Replace keyboard shortcut also needs to work as a repeater when held down–as it does in OpenOffice.
Comment 1 Durgapriyanka 2019-12-09 16:21:31 UTC
Thank you for reporting the bug. I can reproduce in

Version: 6.4.0.0.alpha1+ (x86)
Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
	

and in

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 2 Dieter 2019-12-10 07:37:35 UTC
(In reply to Durgapriyanka from comment #1)
> Thank you for reporting the bug. I can reproduce in

=>NEW