JQuery trigger event performance on document

Question

I'm building a publish/subscribe framework in jQuery and I'm wondering if there are performance penalties to triggering and listening to events on the document root?

All articles I can find describe the penalty you obviously get for listening to events on the document level, but triggering them from a more specific element - listening for a "click" for example.

My pseudo code:

$(document).on("myCustomEvent", function() {
    alert("Event triggered");
});
$(document).trigger("myCustomEvent");

My event does not have a fitting home in the DOM but I could always add a dummy element to trigger from/listen to if it's better, but would rather not. What do you think?

Community · Accepted Answer · 2017-05-23 11:47:07Z

1

trigger() propagates up the DOM. It also interacts with all elements matching the object, which can cause conflicts / unexpected behavior. Neither of these are inherent* performance hits -- and since you're using a custom event, you shouldn't have an issue with other elements matching the object. That's really only a problem when trigger() is used with a real event, like trigger('click'). If you're concerned about either of these (bubbling up the DOM or other matching elements), you can use triggerHandler()

This post goes into more detail about the differences between trigger() and triggerHandler()

edited May 23, 2017 at 11:47

CommunityBot

11 silver badge

answered Feb 11, 2016 at 23:15

devlin carnate

8,6637 gold badges55 silver badges106 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

elad.chen Over a year ago

how about namespacing his events too? -> $(..).trigger("ns.click")

Collectives™ on Stack Overflow

JQuery trigger event performance on document

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related