Doing a "return false;" shouldn't hurt anything. Not everyone wants
to stop onclick events on <a> tags, so it doesn't make sense to add
that to Signal. I've added a note about this bug to the docs:
http://trac.mochikit.com/changeset/1230
Thanks,
Beau
On 5-Dec-06, at 5:37 AM, Juergen Schreck wrote:
> Ok, I've done some more testing with the simplified script:
>
> <a id="one" href="#one">one</a>
> <a id="two" href="#two">two</a>
>
> <script type="text/javascript" charset="utf-8">
> $('one').onclick=function(){ return false; };
>
> connect('one', 'onclick', function(e) {
> e.stop();
> alert('one');
> });
>
> connect('two', 'onclick', function(e) {
> e.stop();
> alert('two');
> });
> </script>
>
>
> Basically, rather than adding the onlick attribute in the markup, I
> added it in code. And it works properly with Safari 1.3+ and still
> works with others. The question now becomes if this is some MochiKit
> could/should handle transparently? There's a lot of pre-2.0.4
> Safari's out there...
>
> I guess it would be an exception in connect for Safari if the source-
> element is an <a> and the event is 'onclick'.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
