Bug 189522 - [Presentations] Outline View looks duplicated for a few seconds before Welcome Page is opened
Summary: [Presentations] Outline View looks duplicated for a few seconds before Welcom...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 trivial (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-05-28 18:01 EDT by Karen Stutesman CLA
Modified: 2019-09-06 16:07 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karen Stutesman CLA 2007-05-28 18:01:16 EDT
Build ID: M20070212-1330

Steps To Reproduce:
1. Open a workspace
2. Open Outline View and put it on the right hand side of the workspace
3. Make sure the Welcome Page is not showing anywhere
4. Help -> Welcome Page

Behavior: Notice the right hand side. Something opens up temporarily to the right of the Outline View that looks like another Outline View just before Welcome Page opens.
Comment 1 Dani Megert CLA 2007-05-29 06:52:25 EDT
Can also bee seen with empty Outline, hence not JDT specific.
Comment 2 Paul Webster CLA 2007-05-29 08:35:46 EDT
I would imagine you are seeing the right-hand sticky-view stack, before the the Welcome view is maximzed

PW
Comment 3 Eric Moffatt CLA 2007-05-29 09:39:49 EDT
The Intro handling has been tagged for a complete review post-3.3. Its current behavior is to open and then to subsequently mazimize (the site has to exist before you can set its state).
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:07:45 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.