Issue 63103 - Mouse Wheel Support of Drop Down List Boxes works not as expected
Summary: Mouse Wheel Support of Drop Down List Boxes works not as expected
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0.3
Assignee: marc.neumann
QA Contact: issues@dba
Keywords: usability
Depends on:
Reported: 2006-03-13 10:16 UTC by christian.jansen
Modified: 2006-06-01 10:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description christian.jansen 2006-03-13 10:16:55 UTC
You need a mouse with a scroll wheel to reproduce this usability issue.

- Add some Drop Down List Boxes to a Writer Document
- Make sure that each Drop Down List Box has 5 items
- Switch of Design Mode
- Move the mouse pointer above text field of the Drop Down List Box
- Move scroll wheel

Bug: Instead of scrolling up or down the whole document, the selected item of
the Drop Down List Box changes.

In a scenario where, depending on the selected item, a different autotext got
inserted into a document -- this behavior can cause unintended and in the worst
case not noticed changes.

The scroll wheel support makes sense for list boxes but not for drop down list

Please compare this with current versions of web browser (Firefox 1.5, IE 6)

So, my recommendation is to switch off the scroll wheel support for Drop Down
List Boxes
Comment 1 marc.neumann 2006-03-13 10:43:39 UTC
According to I change
the Issue Type to Enhancement.

Bye Marc
Comment 2 Frank Schönheit 2006-03-13 12:30:01 UTC
fs->pl: as we agreed (also with CL): Drop Down List Boxes which are focused
should react on the scroll wheel, those which are not focused shouldn't. This
should be done for VCL controls in general, not only for form controls.
Comment 3 philipp.lohmann 2006-03-28 16:08:52 UTC
pl->cj: On second thought i think we should reconsider this; the same problem
applies for e.g. SpinFields and every other control that reacts on the wheel. On
the Unix desktops the behaviour is clear: the wheel action goes to the control
under the mouse, not the focused control. In Windows applications controls
generally do not react on the wheel, only scrollbars do (unless there is some
tweak option i don't know about).

Our current behaviour is consistent with the Unix desktops and especially for
SpinFields i definitely wouldn't want to change that. However changing the
behaviour only for dropdown listboxes is not really a good thing at all.

Maybe it would be better to change the behaviour of document controls only and
then consistently for all controls.
Comment 4 Frank Schönheit 2006-03-29 06:44:56 UTC
This probably means we should imlement this for document controls only. Finally,
it's a document-only problem: you scroll the context of the controls, and while
the control is scrolled "under" the mouse, suddenly scrolling does not affect
the context anymore, but the control. This is a no-issue in dialogs, since there
the "context" (the dialog) is not scrollable (usually).
So, my suggestion would be to introduce a control setting
"NoScrollIfNotFocused", which is set for document-contained controls only.
Comment 5 christian.jansen 2006-03-29 07:07:20 UTC
CJ -> PL,FS: My issue relates to documents only. And this is what we should fix
for 2.0.3. Regarding the behavior of drop down list boxes, spin fields, etc used
on dialogs I strongly suggest to follow the rule that OOo should be a good
desktop citizen on the desktop. Users expect a consistent behavior across
different apps on one platform (desktop).
Comment 6 christian.jansen 2006-03-30 12:04:20 UTC
Reassigned to PL
Comment 7 philipp.lohmann 2006-04-06 12:57:20 UTC
With integration of CWS vcl57 there will be a new MouseSetting
Get/SetNoWheelActionWithoutFocus that you can use in the form layer to implement
Comment 8 Frank Schönheit 2006-04-20 11:24:03 UTC
copied the VCL changes from CWS vcl57 into CWS dba203c, and fixed the issue there.
Comment 9 Frank Schönheit 2006-04-27 13:30:30 UTC
fs-> msc: please verify in CWS dba203c

re-open issue and reassign to msc
Comment 10 Frank Schönheit 2006-04-27 13:30:34 UTC
reassign to msc
Comment 11 Frank Schönheit 2006-04-27 13:30:38 UTC
reset resolution to FIXED
Comment 12 marc.neumann 2006-04-28 13:06:24 UTC
verified in cws dba203c

You can found more information about this CWS in the EIS tool at
Comment 13 marc.neumann 2006-06-01 10:28:06 UTC

this is fixed in the current master. The current master is available at

I close this issue now.

Bye Marc