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!

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 DOM Scripting By Example Adding and Removing Names Registering Names

Amandeep Pasricha
Amandeep Pasricha
14,932 Points

Would the code have worked if we didn't put e as a parameter in the beginning, and proceeded to write input.target?

I know what e does and everything, but there are times when I see (e) being passed as a parameter and not being passed, and I want to know when I should pass it in as one.

Is it the case that if you want to refer to an element that is getting triggered by an event, then you must pass (e) as a parameter?

1 Answer

Steven Parker
Steven Parker
225,712 Points

That's right, the event object (often represented by the parameter name "e") give you access to a number of things, including the target element.

You don't need to include it as a parameter is you don't use it anywhere in your handler. But personally, I like to pass it anyway to acknowledge that the system always supplies it, and to simplify things if code added later needs it.