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

Bug 320323

Summary: dragging editor out of editor area leaves active stack rendering on editor area
Product: [Eclipse Project] e4 Reporter: Susan McCourt <susan>
Component: UIAssignee: Project Inbox <e4.ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: remy.suen
Version: 1.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
screenshot none

Description Susan McCourt CLA 2010-07-19 16:52:42 EDT
Created attachment 174674 [details]
screenshot

Win7, Build id: I20100718-2237

1. Open a file.
2. Close it.
->Note that empty editor area has white, not a blue toolbar.  (Who is active at this point?  No stacks have the blue active bar.) 
3. Click on Package Explorer.
->Package Explorer has active blue bar.  Good.
4. Open a file.
5. Drag it to the Package Explorer stack.
->Now the empty editor area has the blue toolbar.  (Different than step 2, maybe could be justified if the stack is considered active.)
6. Click on the Package Explorer tab.
->Now both the view stack and the editor area have the active blue

At this point the editor area will remain blue whether its active or not.
Even if I close the workbench and reopen it, it is blue.
If I delete the deltas.xml, all is well again.
Comment 1 Remy Suen CLA 2011-02-09 16:32:15 EST
(In reply to comment #0)
> 1. Open a file.
> 2. Close it.
> ->Note that empty editor area has white, not a blue toolbar.  (Who is active at
> this point?  No stacks have the blue active bar.) 

This isn't a problem anymore because activation history has been implemented.

> 4. Open a file.
> 5. Drag it to the Package Explorer stack.
> ->Now the empty editor area has the blue toolbar.  (Different than step 2,
> maybe could be justified if the stack is considered active.)
> 6. Click on the Package Explorer tab.
> ->Now both the view stack and the editor area have the active blue

This is still a problem. See bug 319894.

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