Found some more info here. http://www.codingforums.com/archive/index.php?t-30983.html
Given the date of those posts, and the fact that one of my clients was running 2.0.3 (the latest official version being 2.0.4) it probably was only recently fixed. I don't know if this is some MochiKit can/should work around. Regards, Juergen On Dec 4, 2006, at 11:07 PM, Juergen Schreck wrote: > > Ok, sorry about that. > > On the main page, click 'Community Relations' or 'Media Relations'. > > This click should trigger the next animation overriding what's in > href attribute. Menu images drop out and subpage slides down. > > On the http://www.bwpr.com/new.html page, this doesn't work in Safari > 1.3. Instead of running the animation (executing the 'connected' > onclick signal, it actually tries to follow the href (resulting in a > 404 error). This page work as expected however in Safari 2.0.4, FF > and IE6+. > > On the http://www.bwpr.com/new2.html page, I worked around the Safari > 1.3 problem by rewriting the href attribute. Still work in all the > others too. > > Let me know if I can provide more info. > > And thanks for your patience. > > Regards, > Juergen > > > On Dec 4, 2006, at 10:38 PM, Bob Ippolito wrote: > >> Since this isn't a reduced example, what exactly do you mean by >> "doesn't work"? What are the exact steps to reproduce? >> >> In other words, what should be clicked, what should happen when it's >> clicked, and what currently happens in Safari 1.3? >> >> -bob >> >> On 12/5/06, Juergen Schreck <[EMAIL PROTECTED]> wrote: >>> >>> Ok, this should do. Pretty straightforward stuff. >>> >>> Doesn't work in Safari 1.3: >>> http://www.bwpr.com/new.html >>> >>> Works in Safari 1.3 by rewriting href attribute >>> http://www.bwpr.com/new2.html >>> >>> Thanks in advance for any insight, >>> Juergen >>> >>> >>> On Dec 4, 2006, at 9:48 PM, Bob Ippolito wrote: >>> >>>> The next step is to produce a full example with HTML and >>> JavaScript so >>>> that someone else can reproduce the issue and diagnose it. >>>> >>>> -bob >>>> >>>> On 12/5/06, Juergen Schreck <[EMAIL PROTECTED]> wrote: >>>>> >>>>> >>>>> 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 -~----------~----~----~----~------~----~------~--~---
