Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367091 - [KeyEvents] Some keys events are sent to server incorrectly or not at all
Summary: [KeyEvents] Some keys events are sent to server incorrectly or not at all
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5 M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-19 10:54 EST by Tim Buschtoens CLA
Modified: 2011-12-21 05:26 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2011-12-19 10:54:59 EST 
Keycodes for certain special character keys like "#" and "§" are wrong in RAP.
Keycodes change if SHIFT is hold in RAP, while they don't in SWT. 
Webkit does not send Enter and Escape.
Key-events that are canceled by widgets on the client side may also not be sent. (See Bug 366788.)
Firefox does not send modifiers. (Firefox also does not sent "untrusted" keys - see Bug 329639). In Webkit and IE modifiers repeat, while they do not in SWT.

With the exception of "untrusted" keys (which will be fixed in Bug 329639), most of these can probably be fixed by using "keydown" events as an additional information source in KeyEventUtil.js
Comment 1 Tim Buschtoens CLA 2011-12-21 05:26:19 EST 
Fixed in CVS HEAD.

Client now always sends charcode and keycode, and the server processes them both. Also fixed Modifiers, Escape and Enter (except for firefox when untrusted).
Events are currently still only processed on keypress, because the redispatch-mechanism in ASyncKeyEventUtil makes it hard to change that. Therefore Bug 366788 is still valid.