Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 140061 - [Help] Double clicking on the context help button tramples dialogs
Summary: [Help] Double clicking on the context help button tramples dialogs
Status: RESOLVED DUPLICATE of bug 140306
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-03 15:47 EDT by Bogdan Gheorghe CLA
Modified: 2006-05-23 10:30 EDT (History)
0 users

See Also:

Attachments
Before/After pic of squashed dialog (26.83 KB, image/png)
2006-05-03 15:48 EDT, Bogdan Gheorghe CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Gheorghe CLA 2006-05-03 15:47:50 EDT 
I20060428-1315

If you have context help open on any dialog and double click on the context help button, it will collapse the dialog back to its original size (pre-context help). In doing so, it obliterates a good portion of the dialog in an effort to fit the context help in.

Repro steps: 

1. Open up Window>Preferences
2. Click on the context help button -> the tray window will appear
3. Double click on the context help button -> notice how it squeezes itself back into the original dialog size.
Comment 1 Bogdan Gheorghe CLA 2006-05-03 15:48:34 EDT 
Created attachment 40288 [details]
Before/After pic of squashed dialog
Comment 2 Curtis d'Entremont CLA 2006-05-03 19:31:58 EDT 
It seems if you double click anywhere in the button bar it will resize the dialog; it seems to be kicking in even when double clicking on the help button. Need to investigate why dialogs do this and how to avoid this when clicking on help. Post-3.2.
Comment 3 Curtis d'Entremont CLA 2006-05-23 10:30:12 EDT 

*** This bug has been marked as a duplicate of 140306 ***