I am having difficulty with events on a button. I have a "Print" button, and
having a listener attached to the "execute". Inside the listener, I open a
window (or tab) to receive a .PDF file. If I mouseclick the button, the
listener is fired, and everything works OK, the window opens and eventually
gets its .PDF.

However, if I TAB to the button and hit the RETURN key, the same listener is
fired, BUT the window is blocked by my popup blocker (IE8 and FF3.5). If I
TAB to the button and hit the SPACE key, the listener is fired and the
window appears in FF, but is blocked in IE8.

So, I thought I'd add another listener, for the "keyup" event, because with
the 'execute' listener in place, the event doesn't fire until you release
the SPACE/RETURN keys. After adding the 2nd listener, BOTH listeners are
fired, but the 'execute' listener is fired first.

We read (I think the IE docs) recently that popup blocker can be avoided if
the window is opened in response to a user-initiated event, so that if we
open the window in the first event handler, (e.g. mouseclick => execute
handler) it works fine, but if the execute handler is invoked indirectly (by
capturing key event, then firing the execute event) it is no longer
considered user-initiated and thus the popup blocker fires.

It seems that somewhere in qooxdoo, something must be catching the key event
and redirecting it to the 'execute' event before the event listener for my
key event is invoked. Is this something that can be avoided? The real
problem here is that the popup blocker stops display of the .PDF file; I
don't really care if I need to have one event listener or two or more, but
customer is quite unhappy about the popup blocker.
Ken
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to