The current Seamonkey architecture tries to handle navigation keys as Virtual Keys (WM_KEYUP/WM_KEYDOWN) messages. This prevents input methods from ever seeing backspace events, so Japanese users can't correct their input. *ALL* key events, including Navigation events have to be handled after input methods have a chance at them - this means they have to be handled on the WM_CHAR event for Windows.

Changed from P3 to P1. We need the keyboard events fixed ASAP because the Japanese input methods depend upon this.

The WM_CHAR part of this is being fixed. Tague, still need you to get back to me on how to handle navigation keys which don't fire a WM_CHAR.

Check to see if it is handled by the default window proc - if it is, leave it alone, otherwise process to your hearts cotnent.

Okay. Unfortunately processing the event through the default proc *before* going to the content system is a pretty major change. We currently handle all events before default processing. I'm going to push this to M5 while we think about this.

Cross reference to related bug: http://bugzilla.mozilla.org/show_bug.cgi?id=3546

Sorry, mistakenly closed.

Moving off M5 radar since Tom is out of town.

fixed as part of the big keyboard whackage at least. marking verified