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

Bug 376100

Summary: Find/replace dialog buttons don't activate after first match found using keyboard accelerator
Product: [Eclipse Project] Platform Reporter: Scott Van Wart <silvaran>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, ericwill
Version: 4.2Keywords: triaged
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Scott Van Wart CLA 2012-04-04 11:56:21 EDT 
Build Identifier: 20110615-0604

When a match is found using the keyboard shortcuts to trigger accelerators, sometimes the Replace/Find and Replace buttons stay greyed until the next match.

If you enter the find dialog with some text selected it won't occur.  Sometimes I've had to open a new editor window to get it to occur again after failing to reproduce it.

Running Ubuntu 11.10 64-bit with xfce4 (xubuntu).

Reproducible: Sometimes

Steps to Reproduce:
1. Type some text in an editor (Java, SQL, etc.) as a replacement candidate.
2. Ctrl+F to bring up the Find/Replace dialog.
3. Type some text that will match in the Find field.
4. Hit tab to go to the Replace with field, and type some text.
5. Alt+N to trigger the "Find" button.
6. Note that a match is found, but the Replace/Find and Replace buttons are still greyed out.
Comment 1 Dani Megert CLA 2012-04-05 04:06:33 EDT 
I've never seen this and was not able to reproduce this on Linux and Windows 7 using 3.7.2 and 4.1.2. Can you please try with one of those?

Maybe it's specific to Ubuntu. If so, this would rather be a problem in SWT than in Platform Text.
Comment 2 Eric Williams CLA 2018-06-15 15:04:00 EDT 
(In reply to Dani Megert from comment #1)
> I've never seen this and was not able to reproduce this on Linux and Windows
> 7 using 3.7.2 and 4.1.2. Can you please try with one of those?
> 
> Maybe it's specific to Ubuntu. If so, this would rather be a problem in SWT
> than in Platform Text.

I cannot reproduce the issue either. Please file a new bug against 4.8 if the issue happens on GTK3.22.