Bug 191536

Summary: swt bug: buttons on ON_TOP shells aren't clickable
Product: [Fedora] Fedora Reporter: Anthony Green <green>
Component: eclipseAssignee: Ben Konrath <ben>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: tromey
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: libswt3-gtk2-3.1.2-1jpp_15fc Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-06-01 16:13:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 189582    
Attachments:
Description Flags
Kludgy patch none

Description Anthony Green 2006-05-12 19:30:05 UTC 
Description of problem:
This was found in Azureus.  The following page contains a sample program
that creates an ON_TOP shell with a close buttont on it.  The close button
doesn't not appear to be receiving mouse events.
http://www.java2s.com/Code/Java/SWT-JFace-Eclipse/SWTShellcreateanonrectangularwindow.htm

Version-Release number of selected component (if applicable):
libswt3-gtk2-3.1.2-1jpp_13fc


How reproducible:
Always

Steps to Reproduce:
1.Compile and run the referenced test case.
2.
3.
  
Actual results:
Window with close button appears.  Close button doesn't work.

Expected results:
Close button should work.

Additional info:
Comment 1 Anthony Green 2006-05-19 18:11:09 UTC 
Rolling gtk2 back to gtk2-2.8.15-1 solves the problem.
Comment 2 Anthony Green 2006-05-24 13:15:21 UTC 
Created attachment 129928 [details]
Kludgy patch

This patch (suggested by the upstream bugzilla) seems to solve the problem.
Comment 3 Ben Konrath 2006-06-01 15:26:44 UTC 
I added the patch to the latest FC5 update (3.1.2-1jpp_15fc). Can you please
verify that this is fixed and close the bug if is? Thanks.
Comment 4 Anthony Green 2006-06-01 16:13:10 UTC 
Yes, this is fixed - thanks!