Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript jQuery Basics (2014) Creating a Password Confirmation Form Perform: Part 1

Posted by fbriygig
fbriygig
15,370 Points

Is there any disadvantage to using .on('focus keyup') rather than .focus().keyup()?

I've been previously been taught that the on() method is the best way to attaching event handlers. So my code looks like:

$('#password').on('focus keyup', passwordEvent);

rather than:

$('#password').focus(passwordEvent).keyup(passwordEvent);

Am I following best practice? Do I need to rethink this?

1 Answer

lakindujayathilaka
lakindujayathilaka
15,244 Points

The on() method attaches one or more event handlers for the selected elements and child elements. the on() method is the new replacement for the bind(), live() and delegate() methods. I recommend using the .on() method because the on method will work for both current and FUTURE elements (like a new element created by a script) hope i helped

Dan Johnson
Dan Johnson
9,385 Points

Keep calm

and

call .on()

Is a sticker I have on my monitor to encourage me to do it the right way and not be lazy. :)