On Dec 4, 2006, at 8:04 PM, Bob Ippolito wrote:
> returning false is not how that works. You're supposed to call
> e.stop() (or stopPropagation or preventDefault depending on if you
> want just one of them).
Bob, that's right. And I am doing that. Here's an excerpt of
app.menu_action:
menu_action: function(e) {
e.stop();
el=e.src();
el.blur();
// more stuff ....
return false;
}
So I'm doing all those things, but still at least confirmed in Safari
1.3 the link is executed before the onclick event.
Workarounds I've come up with so far:
- rewrite href attribute to "#" when making connecting the signal
- forget signal and put "onclick" attribute in the markup (silly
enough, but makes it work)
Something doesn't smell right. But what is it?
Juergen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~----------~----~----~----~------~----~------~--~---
