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 trialarmand Rodriguez
7,830 PointsAny drawbacks to alternative method
I had an alternative way and it seemed to work for me. I was just wondering if there would be problems with inserting an 'if' statement into the 'edit' 'else-if statement'. Heres my code:
ul.addEventListener('click', (e) => {
if (e.target.tagName === 'BUTTON') {
const button = e.target;
const li = button.parentNode;
const ul = li.parentNode;
if (button.textContent === "remove") {
ul.removeChild(li);
} else if (button.textContent === "edit") {
const span = li.firstElementChild;
const input = document.createElement('input');
input.type = 'text';
input.value = span.textContent;
li.insertBefore(input, span);
li.removeChild(span);
button.textContent = 'save';
button.addEventListener ('click', (e) => {
if (e.target.textContent === 'save') {
span.textContent = input.value;
li.appendChild(span);
li.insertBefore(span, input);
li.removeChild(input);
button.textContent = edit;
}
});
}
}
});
1 Answer
Steven Parker
231,275 PointsIt's not the "if" statement that makes the difference here, it's that fact that it is part of a completely separate event handler that gets attached as part of the "edit" button processing.
This may work, but deviates from the point of the original code, which was to have a single delegated handler that would take care of all the buttons, and not require additional handlers to be set up later.