Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364731

Summary: [find/replace] Replace disabled after Find/Replace dialog loses focus
Product: [Eclipse Project] Platform Reporter: John Arthorne <john.arthorne>
Component: TextAssignee: Platform-Text-Inbox <platform-text-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: daniel_megert, markus.kell.r, remy.suen
Version: 1.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
Screen shot none

Description John Arthorne CLA 2011-11-24 11:43:20 EST 
I20111110-2200

1) Open an editor with text in it
2) Ctrl+F to open search dialog
3) Enter some text in "Search" and "Replace" fields
4) Click on another view to cause search dialog to lose focus
5) Click back in the search dialog

-> The replace field is greyed out, and all the buttons are greyed out.
Comment 1 John Arthorne CLA 2011-11-24 11:43:45 EST 
Created attachment 207488 [details]
Screen shot
Comment 2 Remy Suen CLA 2011-11-24 13:13:08 EST 
Happens in 3.x also.
Comment 3 Dani Megert CLA 2011-11-28 04:25:27 EST 
Wow, it took 10 years until someone found that bug! Broken since 1.0.
Comment 4 Markus Keller CLA 2011-12-02 15:28:30 EST 
Is it really a bug? I think it's been designed like this.

The Find/Replace dialog retargets to the active part. You can e.g. search for something in one editor and then go to another editor or e.g. to the Console view and then continue your Find/Replace task. If the selected part doesn't support the Find/Replace dialog, the controls are grayed out.

One could argue that the Replace field shouldn't be grayed out if no target is available, but it's already grayed when the target editor is read-only.
Comment 5 John Arthorne CLA 2011-12-02 16:06:24 EST 
It definitely felt like a bug from an end user perspective. I wasn't aware that the dialog automatically retargeted to the selected part. I just clicked elsewhere to check something, and when I came back to the Find/Replace dialog it seemed to broken. I had to close/reopen the dialog to get it working again (it turns out I could have clicked on the editor behind the dialog and this would have worked). Maybe the dialog should only retarget if I switch to a part that actually supports search/replace (another editor, etc). If I click on a view like the Package Explorer the dialog would remain associated with the editor...
Comment 6 Dani Megert CLA 2011-12-05 04:01:09 EST 
(In reply to comment #4)
> Is it really a bug? I think it's been designed like this.
Yes and yes ;-).

The bug is that some fields are still editable while there is no way to actually start the search.
Comment 7 Lars Vogel CLA 2019-11-14 03:41:58 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.