Skip to main content

Performance difference between jQuery"s .live("click", fn) and .click(fn)



I love the new live event in jQuery 1.3. The question I have is the performance of this event. I know the advantages of using live over click/bind('click') but is there a performance hit for using it over click/bind('click')?





If not, why would you ever use click or bind('click')?



Source: Tips4all

Comments

  1. If not, why would you ever use click
    or bind('click')?


    Because $.live() has some significant disadvantages



    Live events do not bubble in the traditional manner and cannot be
    stopped using stopPropagation or
    stopImmediatePropagation. For example,
    take the case of two click events -
    one bound to "li" and another "li a".
    Should a click occur on the inner
    anchor BOTH events will be triggered.
    This is because when a
    $("li").bind("click", fn); is bound
    you're actually saying "Whenever a
    click event occurs on an LI element -
    or inside an LI element - trigger this
    click event." To stop further
    processing for a live event, fn must
    return false.
    Live events currently only work when used against a selector. For
    example, this would work: $("li
    a").live(...) but this would not:
    $("a", someElement).live(...) and
    neither would this:
    $("a").parent().live(...).

    ReplyDelete
  2. See this.

    As for why you would ever use click or bind instead of live, the answer is because you don't need the extra functionality.

    ReplyDelete
  3. You should read this very good answer in this similar thread:

    Is binding events in jQuery very expensive, or very inexpensive?

    ReplyDelete
  4. Just a notice: there is a firebug extension which shows all attached events on a page: http://robertnyman.com/inline-code-finder/

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex