Selecting DOM Elements

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(‘img.gallery’); 

Happy Coding!

Clay Hess

More To Explore

Code

A Quick Tour of the Web Encoding API

Modern web apps live at the boundary between JavaScript strings and raw bytes. The Web Encoding API exists to make that boundary explicit and safe: it lets you encode a string into UTF‑8 bytes and decode bytes back into text. Importantly, these operations aren’t symmetrical—encoding targets UTF‑8, while decoding can interpret UTF‑8 and many legacy encodings. Alongside the synchronous TextEncoder and TextDecoder, the platform also provides stream-based variants for processing text incrementally as data arrives.

Script Proofread And Sentence Grammar Spell Check
Code

EditContext API: A New Foundation for Custom Web Editors

The experimental EditContext API gives developers a new foundation for building custom rich text editors by separating text input and selection from rendering. Instead of relying on contenteditable, you attach an EditContext to a focusable element and manage your own text model, selection state, and UI updates—while still receiving browser-grade events for typing, caret movement, and IME composition. This demo highlights the core event flow and why character bounds matter for accurate input UI, especially in custom-rendered editors.

Share This Post

small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

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

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.