Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 378842 - Opening first editor view with Type Browser triggers incorrect scrolling
Summary: Opening first editor view with Type Browser triggers incorrect scrolling
Status: CLOSED DUPLICATE of bug 375576
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 10:09 EDT by Christian Hartmann CLA
Modified: 2012-05-08 10:35 EDT (History)
1 user (show)

See Also:


Attachments
screenshot (62.52 KB, image/png)
2012-05-08 10:10 EDT, Christian Hartmann CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Hartmann CLA 2012-05-08 10:09:47 EDT
Build Identifier: Version: 4.2.0 Build id: I20120315-1300

I found a strange scrolling-behaviour and difference between Eclipse 3.7.1/3.8 and 4.2 while opening the first editor view by using the type browser. Further details see below under "Steps to reproduce".

Reproducible: Always

Steps to Reproduce:
(you need at least one Java project in your workspace)

1. Open Java perspective
2. Rearrange views, so that the package explorer "steals" width of the editor view (~50% of the workspace) and the editor probably needs to scroll horizontaly
3. Open Type-Browser and open a type, for example java.lang.Object

Now the first editor view opens, selects the type name AND scrolls to the right!

The problem occurs only in the first editor view. Opening a second editor view afterwards (java.lang.String) in the same way works correctly (not scrolling to the right)

It does not depend on the type you are opening (i.e. you can switch first and second type in the example) but the editor needs to scroll.

Opening a type via package explorer works correctly, probably because the type name is not selected (?).
Comment 1 Christian Hartmann CLA 2012-05-08 10:10:58 EDT
Created attachment 215259 [details]
screenshot
Comment 2 Dani Megert CLA 2012-05-08 10:35:33 EDT

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