Bug 542428 - Disable mouse scroll on the PDE product editor for Product and Application
Summary: Disable mouse scroll on the PDE product editor for Product and Application
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: bugday, helpwanted, usability
Depends on:
Blocks:
 
Reported: 2018-12-05 07:11 EST by Lars Vogel CLA
Modified: 2018-12-13 04:31 EST (History)
3 users (show)

See Also:


Attachments
Screenshot (18.35 KB, image/png)
2018-12-05 07:11 EST, Lars Vogel CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2018-12-05 07:11:26 EST
Created attachment 276828 [details]
Screenshot

In the product editor, a common error is that someone unintentially moves the mouse over the Product and Application field and scroll via the mouse wheel. In most cases they want to scroll the editor and the change in the application and product is not desired.

If the mouse is above Product or Application it changes the selection. Mouse scroll should not be considered in these fields.
Comment 1 Julian Honnen CLA 2018-12-05 07:19:26 EST
You can scroll through the combo just by hovering over it? On Win7 (with 4.10 RC1) the mouse wheel event is only intercepted when the combo has been focused first.
Comment 2 Lars Vogel CLA 2018-12-05 07:38:39 EST
(In reply to Julian Honnen from comment #1)
> You can scroll through the combo just by hovering over it? On Win7 (with
> 4.10 RC1) the mouse wheel event is only intercepted when the combo has been
> focused first.

On Windows 10 hovering over the combo is sufficient to scroll it via the mouse wheel. Win7 behaviour sounds correct, maybe we have a SWT/Win10 bug here.
Comment 3 Moritz Aleithe CLA 2018-12-05 07:40:55 EST
It's happening on Win 10 on all comboboxes I know, also in .NET Applications. I think it's more of a feature than a bug (in general, not in this exact case)
Comment 4 Lars Vogel CLA 2018-12-13 04:31:23 EST
Thanks Moritz for the info. If that is an Win10 feature, we should not mess with it.