Hi Gene,
Pretty much right on.
To expand a bit more, we have a fairly large body of users who use IE* as
their browser, and navigate via the TAB (keyboard) interface, rather than
using a mouse. After TABbing to a button, the standard keyboard procedure to
invoke the button's function is to hit either the SPACE (spacebar) key, or
the RETURN key. Unfortunately, in IE* there seems to be no way to capture a
SPACE key event directly, and attempt to open a window without getting the
popup blocker to block the window.
Using FF, I've been able to capture all three - mouse, SPACE, and RETURN as
native events, and bypass the popup blocker.
Using IE* I've only been able to bypass popup blocking with the mouse and
RETURN events, so I was hoping that by capturing a SPACE event, and then
simulating a mouse event, that the mouse event handler would be able to open
the window successfully. Another possible approach would be to simulate a
RETURN event, since I have been able to launch the window successfully from
either mouse or RETURN events.
In IE, it's even uglier (imagine that!) because if you respond to the popup
dialog with "Yes, show me the popup", it reloads the entire web page from
scratch, discarding any of the user's work to that point.
So, the real statement of my mission is to be able to capture a SPACE
keyboard event, and somehow get it to bypass the popup blocker when opening
a new window. Should be easy, but I've working off and on for a solution to
this for almost 3 months at this point.
Ken
On Mon, Dec 28, 2009 at 8:26 AM, Gene Amtower <g...@pc-backup.com> wrote:
> Andreas,
>
> I think it was because his browser security was blocking the event with a
> confirmation popup when it didn't come from a native click response, and he
> wanted to avoid the popup confirmation dialog by replicating the mouse click
> rather than running the code programmatically.
>
> I could be mistaken, but I think that was stated in the original message to
> the ML.
>
> Thanks for confirming that this is a problem, though. Doesn't anyone have
> a workaround to get the mouse event to fire as it should? We have these
> event methods available in the framework, so why isn't there a way to get
> them to fire as intended in this instance?
>
> HTH,
>
> Gene
>
>
> On Mon, 2009-12-28 at 10:40 +0100, Fink, Andreas wrote:
>
> Hi Ken,
> I must confirm, firing a event programmatically is a mystery of qooxdoo ☺
> Especially user events like mouse and key events.But why you simply define
> your handler function like this (tested in playground):
> var button1 = new qx.ui.form.Button("First Button",
> "icon/22/apps/internet-web-browser.png");// Document is the application
> rootvar doc = this.getRoot();// Add button to document at fixed
> coordinatesdoc.add(button1,{ left : 100, top : 50});// Add an event
> listenermyMouseupHandler = function(e) { if (e instanceof
> qx.event.type.Event) { alert("event fired by user!"); } else {
> alert("handler invoked programmatically!"); }}button1.addListener("mouseup",
> myMouseupHandler);
> //invoke mouseup handler programmaticallymyMouseupHandler();
> Regards,Andreas
> Von: Ken MacDonald [mailto:drken...@gmail.com] Gesendet: Donnerstag, 24.
> Dezember 2009 22:01An: qooxdoo-de...@lists.sourceforge.netbetreff: Re:
> [qooxdoo-devel] artificially getting to a listener
> Hi Gene,Still a mystery. I did find an interesting site with a wealth of
> general info about the differences between FF and IE in event handling, and
> they have a javascript package called "Unified Event Model" which attempts
> some workarounds to make IE event handling much more Firefox-like, which in
> turn is much more W3C-like. That site is:
> http://www.jslab.dk/projects.php
> However, I don't know how well qooxdoo would interact with UEM, as well as
> how to automagically bring it in via fooling with generate.py, maybe. Also,
> not sure if UEM even handles this particular event properly.
> That said, I second the idea of having more comprehensive doc around some of
> the more complex areas, such as events. I like your "concise to the point..."
> statement. Some real-life examples, even lifted from the test suite, would go
> a long way toward making this stuff more understandable.KenOn Thu, Dec 24,
> 2009 at 3:45 PM, Gene Amtower <g...@pc-backup.com> wrote:Ken,
> Did you ever figure this out yesterday? From trying to find the answer in
> the manual, I think some additional knowledge and examples is needed in the
> section on events - it's rather concise to the point of not being helpful.
> Some examples in the manual would be helpful, as always. On the other hand,
> something in the demo area would also be nice, as there's nothing there in
> terms of programmatically firing an event.
> Anyone out there have example code of programmatically firing events on
> widgets, where you actually got it to work?
> Thanks,
> Gene
>
> On Wed, 2009-12-23 at 17:58 -0500, Ken MacDonald wrote:Thanks Gene,That gets
> rid of one bunch of errors. The event's init() method doesn't document what
> the array should contain, or if it's even necessary, as it has a null default
> - the fireEvent() doesn't toss errors now, but still doesn't appear to
> work..... the listener for the 'mouseup' event is still not getting called.Ken
> On Wed, Dec 23, 2009 at 5:25 PM, Gene Amtower <g...@pc-backup.com> wrote:Ken,
> Been messing around with this trying to help you sort it out, and in this
> case I think you need a third parameter in qx.eventRegistration.fireEvent()
> of qx.event.type.Mouse, as the default third parameter is
> qx.event.type.Event, per the API.
> However, at that point you'll get another error because you also need to
> provide an array of parameters for the event's Init() method, which I can't
> figure out.
> Maybe this will get you closer to working it out.
> HTH,
> Gene
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer CommunityTake
> advantage of Verizon's best-in-class app development supportA streamlined, 14
> day to market process makes app distribution fast and easyJoin now and get
> one step closer to millions of Verizon
> customershttp://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________ qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> ------------------------------------------------------------------------------This
> SF.Net email is sponsored by the Verizon Developer CommunityTake advantage
> of Verizon's best-in-class app development supportA streamlined, 14 day to
> market process makes app distribution fast and easyJoin now and get one step
> closer to millions of Verizon customershttp://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________qooxdoo-devel mailing
> listqooxdoo-de...@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> ------------------------------------------------------------------------------This
> SF.Net email is sponsored by the Verizon Developer CommunityTake advantage
> of Verizon's best-in-class app development supportA streamlined, 14 day to
> market process makes app distribution fast and easyJoin now and get one step
> closer to millions of Verizon customershttp://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________qooxdoo-devel mailing
> listqooxdoo-de...@lists.sourceforge.nethttps://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
> qooxdoo-devel@lists.sourceforge.net
> 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
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
