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

Bug 368467

Summary: "Environment" Tab in Run Configurations Window Resizes when different Applications are selected
Product: [Eclipse Project] Platform Reporter: Frank Felicetti <frank.felicetti2>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: trivial    
Priority: P3 CC: paul-eclipse, rrabara
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Frank Felicetti CLA 2012-01-12 11:48:25 EST 
Build Identifier: Version: Indigo Release Build id: 20110615-0604

When looking at environment variables (in the "Environment" tab) for a particular Java Application, selecting another Java Application will cause the entire "Run Configurations" window to grow slightly larger.  Selecting other different applications in the list will cause the "Run Configurations" window to increase in width until it fills the entire screen, at which point it stops.  The "Run Configuration" window's height also appears to reset to a specific height (after it resets to this height, though, it doesn't change afterwards).

Reproducible: Always

Steps to Reproduce:
1. Click "Run > Run Configurations"
2. In the "Run Configurations" window that appears, click on the "Environment" tab in the right-hand pane
3. Select a particular Java Application, JUnit Project, etc. in the left-hand side of the pane
4. When clicking on a different application, project, etc., the window's height may change (it will only do this once, if it does change) and the width will increase slightly with each different application, project, etc. that is selected
Comment 1 Michael Rennie CLA 2014-07-24 13:36:50 EDT 
*** Bug 440330 has been marked as a duplicate of this bug. ***
Comment 2 Lars Vogel CLA 2019-11-27 07:48:23 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.
Comment 3 Paul Pazderski CLA 2019-12-05 06:44:17 EST 
Cannot reproduce in I20191204-1800 on Windows 7. Probably fixed meanwhile.