Bug 429592 - [Browser][Mac] KeyDown/Up events have wrong stateMask for modifier key events
Summary: [Browser][Mac] KeyDown/Up events have wrong stateMask for modifier key events
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.4   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-04 14:18 EST by Markus Keller CLA
Modified: 2020-01-06 06:12 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2014-03-04 14:18:49 EST
master and also in 4.3.2.M20140221-1700

In the (WebKit) Browser widget on the Mac, KeyDown/Up events have a wrong stateMask when a modifier key is pressed/released. The pressed key should not be present in the stateMask, and the released key should be present.

(From Felipe Heidrich in bug 367379 comment #2)
> By design, key events are sent to the application *before* they are handled
> by the system. This is important to allow the application to stop a key
> event from being handled by the system.
> So, during the key down event for command key the command bit is not in the
> mask because the system has not yet seen it. Likewise, during the key up the
> command is still set in the mask.

This works fine in other SWT widgets (e.g. Text) and on Windows (IE browser).


I'm pretty sure this bug is the reason for the Platform UI test failures mentioned in bug 428631 comment 4 (but I can't explain why the test don't always fail -- probably some timing issue that prevents the welcome page from taking focus).
Comment 1 Eclipse Genie CLA 2019-12-28 15:39:03 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Lakshmi P Shanmugam CLA 2020-01-06 06:12:20 EST
Still happens with 4.14.