GTK currently generates extra key down and key up events for each repeated key press. Instead, the event chain should look like: keydown, keypress, keypress, keypress, keypress..., keyup This is per the DOM specification and 4.x compatibility: http://www.w3.org/TR/ WD-DOM-Level-2/events.html#Events-eventgroupings-keyevents

Looks like gtk is sending key release events even when no key was released; I wonder if we'll have to go to xlib in order to suppress the fictitious events? Or does gtk have some way of handling this? If we could avoid getting the key release events, then the handle_key_press_event code could suppress the KeyDown event in the case where we already had a KeyDown for that keycode and haven't gotten a KeyUp yet, or something to that effect.

mass-moving most m11 bugs to m12

Mass-moving non-PDT+ bugs to M13

does it still do this now that we are using superwin and generating our own key events?

Yes, it still happens. If you hold a key down, we still get a sequence of key down, key press, key up, key down, key press, key up, etc. as long as the key is held down.

blizzard, could you please look at this?

moving out...

r=syd, fix checked in.

Please ignore the spam. Changing address.

bustage from my reassign

Mass update: changing qacontact to ckritzer@netscape.com

This bug is back from the checkin that fixed bug #46901.

Re-checked in.

Updating QA Contact.

Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.

QA contact updated

verified on build 2001-08-07-08-trunk