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
Gal ParselanyFront End Web Development Techdegree Graduate 20,051 Points
const ul = li.parentNode - why we need this?
why we need this while we already declare the UL in the global scope?
its the same variable
Steven Parker224,936 Points
The "ul" in the handler is not the same variable, it is a new variable with a scope limited to the conditional block it is created in.
Now the global one may contain a reference to the same element, so it could be used instead, but acquiring all the references by traversal in the handler is more of a "best practice". It could avoid future trouble if someone modifying the global code was not aware that the handler code relied on it.