Bug 163536 - [Presentations] Clicking on two editor tab X'es in a row causes editor maximize
Summary: [Presentations] Clicking on two editor tab X'es in a row causes editor maximize
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-06 09:04 EST by Fares Abdullah CLA
Modified: 2019-09-06 15:37 EDT (History)
0 users

See Also:

Attachments
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 Fares Abdullah CLA 2006-11-06 09:04:30 EST 
Eclipse 3.2.1 release
Sun JRE 1.5.0_07-b03
Pentium M

To reproduce:
- Open any two files of roughly the same filename length (ex. "test.txt" and "tset.txt") so that you have two tabs that are of similar width in the editor
- Close both by clicking on the X of the tab of the leftmost one, then the next one (clicking on the same location on the screen)

Notice how the 2nd editor gets maximized instead of closing.

Also:
- Do the above steps, don't move the mouse and double-click (where the tab's X was before it was maximized) to restore the editor.

Notice how the tab closes eventhough it shouldn't.
Comment 1 Fares Abdullah CLA 2008-06-05 01:35:04 EDT 
This is still a problem on:
- Eclipse 3.3.2
- Windows XP
- Intel Core2 Duo T7300, 2GHz
Comment 2 Fares Abdullah CLA 2008-09-02 04:13:37 EDT 
This is still a problem on:
Eclipse Version: 3.4.0
Build id: I20080617-2000
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:37:56 EDT 
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.