Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322438 - [Browser-Webkit] Mouse events have wrong button values (0,1,2 instead of 1,2,3)
Summary: [Browser-Webkit] Mouse events have wrong button values (0,1,2 instead of 1,2,3)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.6.1   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-11 17:24 EDT by Christopher Deckers CLA
Modified: 2010-08-18 11:58 EDT (History)
1 user (show)

See Also:
Silenio_Quarti: review+


Attachments
A test that prints to the console "e.button" for a label and the browser using Webkit (1.76 KB, text/x-java)
2010-08-11 17:25 EDT, Christopher Deckers CLA
no flags Details
patch (1.37 KB, patch)
2010-08-17 15:50 EDT, Grant Gayed CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Deckers CLA 2010-08-11 17:24:45 EDT
Build Identifier: SWT 3.6

When we add a mouse listener to a Browser with Webkit rendering, we receive events with wrong values for the button field.
Normal values are 1, 2 and 3 but we receive 0, 1 and 2.


Reproducible: Always

Steps to Reproduce:
1. Create a Browser.
2. Add a mouse listener that prints e.button
Comment 1 Christopher Deckers CLA 2010-08-11 17:25:38 EDT
Created attachment 176413 [details]
A test that prints to the console "e.button" for a label and the browser using Webkit
Comment 2 Grant Gayed CLA 2010-08-17 15:50:59 EDT
Created attachment 176838 [details]
patch
Comment 3 Grant Gayed CLA 2010-08-17 15:57:25 EDT
Fix released to 3.7 stream > 20100817

Requesting SSQ to review for 3.6.1.  The fix is straight-forward, low-risk to eclipse since it does not use WebKitGTK Browsers by default, and quite fundamental to WenKitGTK users.
Comment 4 Grant Gayed CLA 2010-08-18 11:58:05 EDT
fixed in the 3.6.1 stream > 20100818