Intermediate DOM Manipulation

Back to Lesson Index

🎯 Learning Goals

• Append multiple elements to the DOM to create a to-do list-like application
• Use DOM traversal to listen for events on dynamically created elements

📗 Technical Vocabulary

• Append
• Event
• Object

🗂 Warm Up

List out all the ways you know how to manipulate the DOM so far. Be ready to share out!

🌎 DOM Manipulation

You’ve already come so far with implementing JavaScript to manipulate the DOM! In this lesson, we will take it to the next level. We are going to build a site that can take user input multiple times and keep adding each input to a list. This “To-Do List” is a very common app that developers use as they are learning a new language. Here’s an example of something like what we will build by the end of this lesson:

The scale we are working at is small right now, but this type of functionality is all over the internet. Some examples:

• On Twitter, when a user tweets, they then see a card with that information on it.
• On Google Calendar, when a user adds an event, a color-coded box appears on their calendar at the given time
• On TikTok, when a creator uploads a video, that video is added to the top of their list of videos

.append()

jQuery gives us a function called .append(). If you google append, you’ll see a definition:

verb
add (something) as an attachment or supplement.

The .append() function allows us to append a newly-created HTML element to an already-existing element. Here’s an example of the syntax:

<section class="container">
</section>

var container = $('.container');
container.append(`<p>Hello!</p>`);

As you can see above, we have an empty section element in the HTML document. In JavaScript, we accessed that section element by its class. Let’s break down the next line:

• container - the HTML section we accessed on the previous line
• .append() - this function is being called on the container, so it’s saying: I’d like you to attach something to the container.
• (`<p>Hello!</p>`) - this is the argument that .append() takes, wrapped in back-ticks, an HTML element. Whatever lives inside the back-ticks will be added into the innerHTML of the container.

🌎 Takeaways:

• The three to-dos appeared in the To-Do section and not in the Notes section because .append() was called on the list variable, so the elements were added into that container.
• If backticks aren’t used to enclose the element you want to append, a) the element won’t append, and b) all code written below that line will not be able to run.
• We can append ANY type of HTML element!

When to Append

This is great, but the append is happening right away, so it’s not really helping us build a dynamic to-do list.

We can’t just append directly in our JavaScript file, or as we saw, that HTML will be added immediately. We want to respond to our user with an event listener and handler. Here’s a more realistic example, with a little more going on.

Read through each line of the JavaScript; make sure to reference the HTML, so you know which DOM element we are accessing.

Inside the event handler, we took two important steps:

1. Get the information that the user typed in
2. Append that information (plus some of our own text) inside a p element to the cardContainer.

When we appended the p element, we added a class to it. The CSS file has a rule written for that class, so when the paragraph was appended, it came with styles already applied!

You may have noticed that we can append multiple elements at the same time. Typically, we will see one div or another type of container, wrapping other elements with information, appended to the DOM. It could look something like this:

function appendSomeoneAwesome() {
   var name = $('.name').val();
   var birthday = $('.birthday').val();

  cardContainer.append(`
    <div class="name-card">
      <p class="name">${name} is awesome!</p>
      <p class="birthday">Their birthday is ${birthday}.</p>
    </div>
  `);
}

The code above would append a div that contains two ps to the cardContainer.

Delete a To-Do

The point of a To-Do list is to finish task items and cross them off, so we need to add some functionality on our app that allows users to cross-off, or delete, completed to-dos.

This presents an interesting challenge - we can’t access an element on the DOM with jQuery if it wasn’t on the original HTML document. Since a delete button associated with a given to-do will be created dynamically, we will need to do some DOM traversal.

In the lesson on Forms, we briefly talked about event.preventDefault(). We are going to use something related to that. The event object is a JavaScript object that gets created by the browser when the user interacts with the DOM in such a way as to trigger an event. It holds information about the event itself. A click event object has information like:

• The location that the user clicked (X and Y coordinates)
• The HTML element that the user clicked
• a LOT more!

What we really care about is the HTML element that the user clicked. If the user clicked a delete button, we want to delete the card that belongs to that delete button. We can access the information for the specific element that was clicked on by using event.target.

So, we are going to add this code in:

// access the card container
var cardContainer = $('.card-container');

// listen for a click on the card container
cardContainer.on("click", deleteCard);

function deleteCard() {
  // event.target refers to the element that was clicked on
  // className checks the class that is on an element
  // if it was an element with the class of delete...
  if (event.target.className === "delete") {
    // event.target refers to the element that was clicked on
    // parentNode travels up and looks for the direct parent element
    // then we will remove it's PARENT element, which will be a card
    event.target.parentNode.remove();
  }  
}

Let’s break that code snippet down:

• We placed the event listener on an element that was in the original HTML.
• event.target refers to the element that was clicked on.
• .className looks up the class name that is on an element.
• We used a conditional to check if the element that the user clicked is a delete button.
• .parentNode travels up the HTML and accessed the direct parent of the element that it was called on. In our case, event.target.parentNode will access the card.
• .remove() completely deletes an element from the page. We can not get it back once we do this.

Keep in mind: for this to all work, our JavaScript file would still have all the code to take the user input and add the card!

As a class, let’s discuss how that worked to make sure we are all on the same page.

Clear Input Fields

If it’s been bothering you that the user has to delete the last thing they typed into the input, you’re not alone. We can write code to clear out that field when the user clicks the submit button: We’ll use something like:

var nameInput = $('.name');

nameInput.val("");

The code above would access an element with the class name, and change its value to an empty string.

You’ve learned a lot and have already come so far. Put all your skills together by completing this mini-project below.

Extensions

• Using an object when we get lots of information from our user is a common pattern. Read more about it here!
• As developers write more and more code, it can get difficult to keep track of what is what. It’s important to step back and clean up our code from time to time. Refactoring is a common and important practice for developers. Learn about it here.

Back to Lesson Index