Yes, it is a known issue. see this bug: http://bugzilla.qooxdoo.org/show_bug.cgi?id=4669 it used to be like this for mouse events but it got fixed, somehow the key events were forgotten. I will look if such a bug exists already, if not i will make one and post its number here.
cheers, Gabi P.S. the reason why: compare the TARGET_CHECK static in both these files: http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo/trunk/qooxdoo/framework/source/class/qx/event/handler/Keyboard.js?revision=28889&view=markup and http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo/trunk/qooxdoo/framework/source/class/qx/event/handler/Mouse.js?revision=28889&view=markup as you can see , for the mouse we have "qx.event.IEventHandler.TARGET_DOCUMENT + qx.event.IEventHandler.TARGET_WINDOW" in addition to what we have for keyboard events. adding them to Keyboard handler will remove the warning. The whole thing works because key handlers on the document/window are initialized at the beginning: see this._initKeyObserver(); in the constructer of Keyboard.js. -- View this message in context: http://qooxdoo.678.n2.nabble.com/Warning-There-is-no-event-handler-for-the-event-keydown-on-target-object-HTMLDocument-tp6878736p6879864.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
