I have this code in a standalone single page application:
var search = new qx.ui.basic.Label( this.tr(" Search <#> ") ).set( { rich :
true } );
this.add( search );
search.addListener( "click", function(){ alert("onclick"); }, this);
// search.addListener( "mousedown", function(){ alert("onmousedown"); },
this);
The "this" is an extended "qx.ui.container.Composite" class.
I use it to show a clickable link. It worked fine in version 2.0.4. It
doesn't work in version 3.0.1 like it used to. I can only make the "click"
event fire if I click BOTH mouse buttons at the same time which isn't an
option.
I suspect there is some enclosing parent element/class/object that is
capturing the click event and preventing it from reaching the label but I
don't know where to look. Optionally, a mousedown event works fine if that
is used. The frustrating thing is I cannot replicate this problem in the
playground.
Anyone have any suggestions for properties to set that might free the events
to propagate properly?
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Weird-Click-Behavior-tp7585014.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
