Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7582011
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T18:20:06+00:00 2026-05-30T18:20:06+00:00

I really liked the .live method as it was straightforward and essentially not much

  • 0

I really liked the .live method as it was straightforward and essentially not much different than your standard event handler.

Alas, it was deprecated and I’m left with the .on method.

Basically, I’m loading and dynamically loading content that I’ll need the same event handler triggered on. Rather than add the event handler twice or however many times. .live was great for this, but .on has replaced it and I just can’t seem to get it to work.

check this code:

jQuery('#who_me').live('click', function(){
        alert('test123');
        return false;
    });

should be the same as:

jQuery('#who_me').on('click', function(){
        alert('test123');
        return false;
    });

but when I replace content with the .html method after an ajax call only the live method works.

Can anyone clear this up for me?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T18:20:07+00:00Added an answer on May 30, 2026 at 6:20 pm

    You aren’t using .on() correctly. This is a better implementation if the #who_me object comes and goes.

    jQuery(document.body).on('click', '#who_me', function(){
        alert('test123');
        return false;
    });
    

    The selector you use in the jQuery object for .on() must be an object that is present at the time you install the event handler and never gets removed or recreated and is either the object you want the event installed on or a parent of that object. The selector passed as the 2nd argument to .on() is an optional selector that matches the object you want the event on. If you want .live() type behavior, then you must pass a static parent object in the jQuery object and a selector that matches the actual object you want the event on in the 2nd argument.

    Ideally, you put a parent object in the jQuery object that is relatively close to the dynamic object. I’ve shown document.body just because I know that would work and don’t know the rest of your HTML, but you’d rather put it closer to your actual object. If you put too many dynamic event handlers on the document object or on document.body, then event handling can really slow down, particularly if you have complicated selectors or handlers for frequent events like click or mousemove.

    For reference, the 100% equivalent to your .live() code is this:

    jQuery(document).on('click', '#who_me', function(){
        alert('test123');
        return false;
    });
    

    .live() just installs all its event handlers on the document object, and uses event bubbling to see all the events that happen on other objects in the page. jQuery has deprecated .live() because it’s better to NOT install all your live event handlers on the document object (for performance reasons). So, pick a static parent object that is closer to your object.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've looked at ciui and really liked the way that certain links will slide
I'm having a really big problem with live binding in jQuery 1.4. I want
I really like DevX components, but they are pretty expensive, maybe anyone knows free
I really like the fact that Microsoft has taken a commitment to bring MVC
I really like Xml for saving data, but when does sqlite/database become the better
I really like the way gmail has the archive system implemented. I can archive
I really like how Consolas looks with ClearType enabled but unfortunately it makes everything
I really like the format and type of links from RubyFlow for Ruby related
I really like the Mako templating system that's used in Pylons and a couple
I really like the moq mocking framework. I've used it on several projects. Unfortunately,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.