Selecting DOM Elements

Share This Post

There are several ways to grab DOM elements using the document object. We can use the id…

let myElem = document.getElementById(‘elementId’); 

This will grab the DOM element that has the ID we pass to the getElementById function and stores it in the variable.

We can get elements by the class name…

let myElem = document.getElementsByClassName(‘elementClassName’); 

This will grab all the elements with the class name passed to the getElementsByClassName method. It will return them as an array and store them in the variable. This is the largest difference between grabbing DOM elements by ID versus class. Grabbing them by ID only returns the one element because there can (should) only be one element with that ID on the page. The can be multiple elements with the class name though.

We can also grab by tag name…

let myElem = document.getElementsByTagName(‘p’); 

In this example, we are getting all of the paragraph elements on the page and storing them as an array in the variable.

We can also utilize css selectors with two additional methods…querySelector and querySelectorAll…

let myElem = document.querySelector(‘elementId’); 

In this example, we can grab any element by a css selector. I have the ID in the method, but we can pass a class, a tag or a combination of those. For example, if we would like a paragraph tag with the ID of intro…

let myElem = document.querySelector(‘p#intro’); 

We can also grab several elements…

let myElem = document.querySelectorAll(‘css selector’); 

Again, we can use css selectors. This difference here is we can grab several elements and they return as an array. For example, if we wish to grab all images that have a class of gallery…

let myElem = document.querySelectorAll(‘’); 

Happy Coding!

Clay Hess

More To Explore


Demystifying Scrum User Stories Confirmation: Ensuring Quality and Collaboration

One of the key elements of Scrum is the use of user stories to define the requirements of a system or feature from the perspective of the end user. As teams work through the product backlog, it becomes crucial to confirm the user stories to ensure they meet the desired criteria and are ready for development. In this blog post, we’ll explore the concept of Scrum user stories confirmation and its significance in delivering high-quality products.


The Power of Conversations in Scrum User Stories

At the heart of Scrum lies the concept of user stories, which serve as a means of capturing requirements from the perspective of end-users. However, the true power of user stories lies not just in their written form but also in the conversations that take place around them. In this blog post, we will explore the significance of conversations in Scrum user stories and how they contribute to the success of Agile projects.

Do You Want To Boost Your Business?

drop us a line and keep in touch

Scroll to Top

Need help?

Let's have a chat...


Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 


Begin Your Learning Journey Today!

Come back inside to continue your learning journey.