Link for reference: http://bugzilla.qooxdoo.org/show_bug.cgi?id=1502
I recently got back to looking at this bug, and I have a fix that is working
for me, but I'd like feedback on the correctness of the fix from those more
knowledgeable than I.
qx.event.handler.EventHandler: (added code highlighted in green)
_onselectevent : function(e)
{
if (!e) {
e = window.event;
}
var target =
qx.event.handler.EventHandler.getOriginalTargetObjectFromEvent(e);
// this.debug("Onselect...: " + e.type + " :: " + target + " :: " +
target.getSelectable());
while (target)
{
if (target.getSelectable() != null)
{
if (!target.getSelectable())
{
// this.debug("Stopping: " + e.type);
qx.event.handler.EventHandler.stopDomEvent(e);
return false;
}
break;
}
target = target.getParent();
}
return true;
}
In the case described in the Bug, this function is entered as a result of a
selection event occurring in the browser. It correctly identified that the
element was selectable, therefore it did not stop the DOM event. While the
code (without modifications) worked elsewhere, it seems that in this case, IE
was expecting a return value of "true" instead of "undefined".
Will this produce correct results for all browsers? Should this be an IE-only
code path? Any thoughts or feedback is welcome.
Thanks,
Bryan
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
