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

Bug 370079

Summary: weird scrolling behavior in lists on Kubuntu
Product: [Eclipse Project] Platform Reporter: Stephan Herrmann <stephan.herrmann>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: h.klene, martin.fleurke, remy.suen
Version: 4.2   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Whiteboard:

Description Stephan Herrmann CLA 2012-01-29 15:16:39 EST
Using Eclipse SDK 4.2 M5 on Kubuntu:

Some lists have some unpleasant scrolling behavior:

Preferences > General > Keys

1. in the command list scroll using the mouse wheel or scrollbar
2. click to select a command
3. list snaps to top, so I don't see what I just selected
   (except for the details below, which show that selection worked OK)


Editor Ctrl-E:

1. scroll using the mouse wheel or scrollbar
2. try to click on an entry that just became visible
3. as soon as the mouse moves. the list starts semi-random scrolling,
   so hitting a specific entry is hardly possible.

The second behavior looks like it's also trying to jump to the top but as soon as the movement starts it is stopped by a new implicit selection under the mouse pointer. Random scrolling only ever happens towards the top.

FWIW, I'm using the "classic" scheme due to usability issues in the default scheme.
Comment 1 Remy Suen CLA 2012-01-29 20:56:00 EST
Does this happen in 3.x?
Comment 2 Stephan Herrmann CLA 2012-02-04 16:21:17 EST
(In reply to comment #1)
> Does this happen in 3.x?

I hadn't noticed, but you may be interested in hearing that this got introduced somewhere between 3.8M3 and 3.8M4!

I also tried 4.2M2 where the Keys preference page behaves well, but in that version Ctrl-E in editors still suffers from lack of scrollbars ;-P

Right now I didn't have more versions at hand to narrow down further.
Comment 3 Stephan Herrmann CLA 2012-04-07 19:46:17 EDT
(In reply to comment #2)
> I also tried 4.2M2 where the Keys preference page behaves well, but in that
> version Ctrl-E in editors still suffers from lack of scrollbars ;-P

Using 4.2M6 the bogus jumping behavior in the Ctrl-E list is observable again.
Only chance to use the Ctrl-E list is via the keyboard.
Comment 4 Holger Klene CLA 2012-07-08 12:39:02 EDT
The first issue about Preferences > General > Keys was reported as bug 376474

I cannot reproduce the second issue as the Ctrl+E list closes whenever I select an item. Actually there are at least 3 "editor-lists"
- Ctrl+E
- Shift+Ctrl+E
- Ctrl+F6 with or without shift
But they all work as expected for me.

Version: 4.2.0 Build id: I20120608-1400
Comment 5 Stephan Herrmann CLA 2012-07-10 19:04:47 EDT
(In reply to comment #4)
> The first issue about Preferences > General > Keys was reported as bug 376474

at what time it was already reported as bug 370079 :)
 
> I cannot reproduce the second issue as the Ctrl+E list closes whenever I select
> an item.

If you closely follow comment 0 you see that the problem is *before* selecting an item, not after.

I still see it in 4.2.0.

> Actually there are at least 3 "editor-lists"
> - Ctrl+E

That's the buggy one.

> - Shift+Ctrl+E

no problem here.

> - Ctrl+F6 with or without shift
> But they all work as expected for me.

I didn't know this one but combination of mouse-wheel and mouse-motion is
broken also here.
Comment 6 Holger Klene CLA 2012-07-11 16:44:55 EDT
ups ... admitted, you were faster :-)
Comment 7 Martin Fleurke CLA 2012-10-26 05:15:00 EDT
I can confirm issue 1 (keys) in Ubuntu + Eclipse 4.2.1

I think I have seen issue 2 (ctrl-e) sometimes, but can't reproduce it now on 4.2.1.

I do have another scrolling issue: If you use git history, and search, scrolling is bad too. The item you 'found' disappears from the viewable part. Scrolling is not to top, but neither to the correct place. (bug 388768)
Introduced also in 3.8 / 4.2, not in 3.7
Comment 8 Paul Webster CLA 2012-12-10 09:46:37 EST

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