Bug 344898 - An extra SWT.FocusOut event occurs when I click on a combo box's "down arrow" to show it's list
Summary: An extra SWT.FocusOut event occurs when I click on a combo box's "down arrow"...
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.1   Edit
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
: 98283 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-05 17:26 EDT by Richard Mah CLA
Modified: 2018-12-07 15:06 EST (History)
3 users (show)

See Also:


Attachments
snippet (3.02 KB, text/x-java)
2018-12-07 11:42 EST, Xi Yan CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Mah CLA 2011-05-05 17:26:59 EDT
Build Identifier: 3.6.2

I'm seeing an extra SWT.FocusOut event when I click on the "down arrow" of the combo to reveal it's list.  I'm only seeing this on Linux.  On Windows, I'm seeing the SWT.FocusOut event only when I click off of the combo (which is the expected behavior).

I'm using the combo to edit a cell in a table.  Below is an SWT sample which shows how the combo is being used.  The sample is using a Text but the usage is the same:
http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet124.java?view=co

The extra SWT.FocusOut causes the combo to be disposed when it shouldn't be.  This causes Eclipse to hang on SLES 11.1 and operate improperly on RedHat 6.0

Reproducible: Always
Comment 1 Xi Yan CLA 2018-07-27 15:47:28 EDT
I can reproduce the issue on SWT master, GTK3.22, and Fedora 28.
Comment 2 Xi Yan CLA 2018-12-07 11:42:40 EST
Created attachment 276863 [details]
snippet
Comment 3 Xi Yan CLA 2018-12-07 11:43:59 EST
I cannot reproduce this anymore on Fedora 29, GTK3.24, using SWT master using the attached snippet.
Comment 4 Xi Yan CLA 2018-12-07 15:06:14 EST
*** Bug 98283 has been marked as a duplicate of this bug. ***