[qooxdoo-bugs] [Bug 4041] New: keypress is not a keySequence event but rather a textInput event
Brought to you by:
ecker,
martinwittemann
From: <bug...@qo...> - 2010-08-30 13:23:24
|
http://bugzilla.qooxdoo.org/show_bug.cgi?id=4041 Summary: keypress is not a keySequence event but rather a textInput event Product: framework Version: trunk Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core-event AssignedTo: no...@qo... ReportedBy: adr...@1a... QAContact: qoo...@li... Some description first (not related to qooxdoo). We have 4 keyboard events: keydown, keypress,textInput,keyup. The keydown event occurs when the key is pressed, followed immediately by the keypress event, and possibly the textInput event. Then the keyup event is generated when the key is released. the keydown and keyup events represent keys being pressed or released, while the keypress event represents a character being typed. textInput is a replacement and generalization of keypress. in qooxdoo, the keydown/keypress/keyup fire a keysequence event which is used to identify the key being pressed and textInput event fire a textinput event to check which character was actually pressed. As you see we have a keypress event that is used for something and a textInput that is used for something else. This two should be the same, and used for exactly the same purpose: checking which character was pressed. -- Configure bugmail: http://bugzilla.qooxdoo.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |