OK, here it is. Make sure that popup blocking is on - I used FF3.5 to run
this in the playground. Click on the button with the mouse - a popup window
(or new tab) should appear, and focus will be on the button. Now hit the
space bar and another new tab will appear. Finally, hit RETURN and the popup
blocker should appear and no tab will be created.

In IE8, both SPACE and RETURN cause the popup blocker to appear, neither
works correctly. Mouseclick DOES work correctly, however.

Also, if this would work having the proper behavior (open new tab, be able
to display a .pdf) using a qooxdoo window.Window, that would probably be OK
as well.
Ken

http://demo.qooxdoo.org/current/playground/#%7B%22code%22%3A%20%22%252F%252F%2520Create%2520a%2520button%250Avar%2520button1%2520%253D%2520new%2520qx.ui.form.Button%28%2522First%2520Button%2522%252C%2520%2522icon%252F22%252Fapps%252Finternet-web-browser.png%2522%29%253B%250A%250A%252F%252F%2520Document%2520is%2520the%2520application%2520root%250Avar%2520doc%2520%253D%2520this.getRoot%28%29%253B%250A%250A%252F%252F%2520Add%2520button%2520to%2520document%2520at%2520fixed%2520coordinates%250Adoc.add%28button1%252C%250A%257B%250A%2520%2520left%2520%253A%2520200%252C%250A%2520%2520top%2520%2520%253A%252050%250A%257D%29%253B%250A%250A%252F%252F%2520Add%2520an%2520event%2520listener%250Abutton1.addListener%28%2522mouseup%2522%252C%2520function%28e%29%2520%257B%250A%2520%2520alert%28%2522Hello%2520Planet!%2522%29%253B%250A%2520%2520window.open%28%2522%2522%252C%2520%27_blank%27%29%253B%250A%257D%29%253B%250Abutton1.addListener%28%2522keyup%2522%252C%2520function%28e%29%2520%257B%250A%2520%2520alert%28%2522Hello%2520Mars!%2522%29%253B%250A%2520%2520window.open%28%2522%2522%252C%2520%27_blank%27%29%253B%250A%257D%29%253B%250A%22%7D

On Tue, Dec 22, 2009 at 4:55 AM, Christian Schmidt <
[email protected]> wrote:

> Hi Ken,
>
> I think you are talking about a native window and not from the
> qx.ui.window.Window, right? I'm not sure, but perhaps there is an issue
> with the focus handler, when you are using the keyboard. Could you
> please provide a short code snippet which reproduce your issue. And
> which qooxdoo version do you use?
>
> Thanks,
> Chris
>
> Am 21.12.2009 18:58, schrieb Ken MacDonald:
> > 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
>
>
> --
> Christian Schmidt
> Software Entwickler
>
> 1&1 Internet AG - Web Technologies
> Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
> [email protected]
>
> Amtsgericht Montabaur / HRB 6484
> Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas
> Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver
> Mauss, Jan Oetjen
> Aufsichtsratsvorsitzender: Michael Scheeren
>
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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