I don't completely get the point, custom events don't propagate, and
don't have default behaviors, so none of those 2 functions should
affect the behavior of the handlers. If your intention is to stop the
iteration over the handlers, you could add another function as in
stopIteration or something like that. OO events would be nice, just to
have a small function Event that you can modify it's prototype, that
would match the extensibility of jQuery.fn.
Ariel Flesler
On Oct 17, 5:12 pm, "Jonathan Sharp" <[EMAIL PROTECTED]> wrote:
> $(window)
> .bind('testEvent', function(e) {
> alert('1');
> e.stopPropagation();
> e.preventDefault();
> return false;
> })
> .bind('testEvent', function() {
> alert('2');
> })
> .trigger('testEvent');
>
> The above code doesn't stop the testEvent from triggering the second alert.
> Is the propagation prevention just for standard events such as 'click',
> etc.?
>
> -js
