Understanding The DOM: How Browsers Show Content On-Screen

November 26, 2019

4,506 words

Post contents

Any web application relies on some fundamental technologies: HTML, CSS, and JavaScript. Even advanced front-end JavaScript frameworks such as Angular, React, or Vue will utilize some level of HTML to load the JavaScript. That said, how the browser handles HTML and CSS under-the-hood can be quite the mystery. In this article, I'm going to explain what the browser does to understand what it should show to the user.

If you're unfamiliar with HTML, CSS, or JavaScript, you may want to take a look at our post that introduces these three items. They'll provide a good foundation for this article for newcomers to the programming scene or folks who may not be familiar with what those languages do.


Just as the source code of JavaScript programs are broken down to abstractions that are more easily understood by the computer, so too is HTML. HTML, initially being derived from SGML (the basis for XML as well), actually forms a tree structure in memory in order to describe the relationships, layout, and executable tasks for items in the tree. This tree structure in memory is called the Document Object Model (or DOM for short).

For example, when you load a file similar to this:

<!-- index.html --><!-- ids are only added for descriptive purposes --><main id="a">	<ul id="b">		<li id="c">Item 1</li>		<li id="d">Item 2</li>	</ul>	<p id="e">Text here</p></main>

The browser takes the items defined in the HTML and turns them into a tree that the browser understands how to lay out and draw on the screen. That tree, internally, might look something like this:

A chart showing the document object model layout of the above code. It shows that the 'main' tag is the parent to a 'ul' tag, and so on

This is an oversimplified example of how the browser interprets HTML, but gets the job done to convey introductory information.

Let's see how this is done.

At the root of any HTML file, you have three things: tags, attributes, and text content.

<!-- A "header" tag --><header>  <!-- An "a" tag with an "href" attribute -->  <a href="example.com">    <!-- A text node -->    Example Site  </a></header>

When you type a tag, like <header> or <a>, you're creating an element node. These nodes are then composed to create "leaves" on the DOM tree. Attributes are then able to manually add information to these nodes. When you have one element node inside of a separate one, you add a "child" to said node. The relationship between the nodes allows metadata, CSS properties, and more to be preserved.

There's also the idea of a "sibling" node. When a node's parent has more than one child, those other nodes are that child node's "siblings".

A chart showing the relationships between parents and siblings

Altogether, the terminology used to refer to the nodes and their various relationships is extremely similar to the terminology often used with family trees.

There are some rules for the tree that's created from these nodes:

  • There must be one "root" or "trunk" node, and there cannot be more than one root
  • There must be a one-to-many relationship with parents and children. A node:
    • May have many children
    • Cannot have more than one parent
  • A non-root node may have many siblings as a result of the parent having many children
A chart showing the aforementioned rules of the node relationships
How It's Used By The Browser

This tree tells the browser all of the information it needs to execute tasks in order to display and handle interaction with the user. For example, when the following CSS is applied to this HTML file:

// index.css#b li {	background: red;}
<!-- index.html --><main id="a">	<p id="e"></p>  <ul id="b">    <li id="c"></li>    <li id="d"></li>  </ul></main>

While moving through the tree, the browser can keep track of the fact that it needs to find an element with the ID of b and then mark its <li> children with a red background. They're "children" because the DOM tree preserves the relationship defined by the HTML.

A chart showing the 'ul' tag highlighted in green with the children 'li' tags marked in red

The <ul> element is marked as green just to showcase that it is the element being marked by the first part of the selector.

Typically, the browser will "visit" it's nodes in a specific order. For example, in the above chart, the browser might start at the <main> tag, then go to the <p> tag, then visit the <ul> tag, and finally the two children in order from left-to-right (<li id="c"> , <li id="d">).

The browser, knowing what CSS to look for, is able to see the <ul> with the correct ID and know to mark its children with the correct metadata that matches the selector with the relevant CSS.

This tree relationship also enables CSS selectors such as the general sibling selector (~) or the adjacent sibling selector (+) of find siblings to a given selector.

A showcase of the above selectors and how they always look forward, never behind

Interestingly, one of the questions that I've often heard asked concerns a "parent selector". The idea behind the question is that the direct child selector (>) exists, so why not have the ability to select any parent of .classname selectors?

The answer behind that? Performance. The W3 Consortium (the organization that maintains the HTML and CSS standard specifications) points to the tree structure of the DOM and the algorithm used by the browser to traverse the DOM (or, "visit" the nodes in order to figure out what CSS to apply) as not being performant when allowing parent selectors.

This happens because browsers read from top-to-bottom in the DOM and apply CSS as they find matching nodes; CSS doesn't command the browser to do anything to the DOM, but rather provides the metadata for the DOM to apply the relevant CSS when the browser comes across that specific node.

As mentioned before, they start at the root node, keep notes on what they've seen, then move to children. Then, they move to siblings, etc. Specific browsers may have slight deviations on this algorithm, but for the most part, they don't allow for upwards vertical movement of nodes within the DOM.

Using The Correct Tags

HTML, as a specification, has tons of tags that are able to be used at one's disposal. These tags contain various pieces of metadata internally to provide information to the browser about how they should be rendered in the DOM. This metadata can then be handled by the browser how it sees fit; it may apply default CSS styling, it may change the default interaction the user has with it, or even what behavior that element has upon clicking on it (in the case of a button in a form).

Some of these tag defaults are part of the specification, while others are left up to the browser vendor to decide. This is why, in many instances, developers may choose to use something like normalize.css to set all of the element CSS defaults to an explicit set of defaults. Doing so can avoid having the UI of a webpage look different from browser to browser thanks to deviations on default CSS styling on specific tags.

This metadata is also why it's so important that your application utilizes the expected HTML tags and not simply default to <div>s with CSS or JavaScript applied to simulate other items. Two of the biggest advantages to responsibly utilizing the metadata system the browser has built into it by using the correct tags are search engine optimization (SEO) and accessibility.

Take the following example:

<div>	<div>Bananas</div>	<div>Apples</div>	<div>Oranges</div></div>

In this example, your browser only knows that you're looking to display text on-screen. If someone utilizing a screen reader reaches the site, the browser doesn't know that it should inform them that there are three items in a list (something that people with low vision would greatly value to know, in order to tab through the list effectively) as you've done nothing to inform the user that it is a list of items: only that it's a set of <div> generic containers.

Likewise, when Google's robots walk through your site, they won't be able to parse that you're displaying lists to your users. As a result, your search rating for "list of best places" might be impacted since the site doesn't appear to contain any list at all.

What can be done to remediate this? Well, by utilizing the proper tags, of course!

<ol>	<li>Bananas</li>	<li>Apples</li>	<li>Oranges</li></ol>

In this example, both the browsers as well as Google's scraper bots are able to discern that this is a list with three list items within it.

While there ARE tags that may potentially impact SEO somewhat significantly, it's unlikely <ul> and <li> would significantly impact your SEO scores.

Needless to say, it's still good to use semantic (correctly tagged) HTML as people that use screen-readers and other assistive technologies benefit greatly from these minor changes. Additionally, it can make code more readable and parsable with automated tools.

We're able to even add further metadata to an element by using attributes. For example, let's say that I want to add a title to the list to be read upon a screen reader gaining focus on the element; we could use the aria-label attribute:

<ol aria-label="My favorite fruits">	<li>Bananas</li>	<li>Apples</li>	<li>Oranges</li></ol>

In fact, the metadata that specific tags have by default can be manually applied to an element of a different type. The metadata that is passed to the browser when using <li> is typically involving that element pertaining to a listitem, using the role attribute, we can add that information to a <div> itself.

<ol>	<div role="listitem">Bananas</div>	<div role="listitem">Apples</div>	<div role="listitem">Oranges</div></ol>

It's worth mentioning that this example is generally considered malpractice. While you may have been able to preserve some of the metadata from a <li> tag in a <div> element, it's extremely difficult to catch all of the defaults a browser might apply to the original tag that may enhance the experience of someone that uses a screen-reader.

This is all to say, unless you have a really good reason for using role rather than an appropriate tag, stick with the related tag. Just as any other form of engineering, properly employing HTML requires nuance and logic to be deployed at the hand of the implementing developer.

Element Metadata

If you've ever written a website that had back-and-forth communication between HTML and JavaScript, you're likely aware that you can access DOM elements from JavaScript: modifying, reading, and creating them to your heart's content.

Let's look at some of the built-in utilities at our disposal for doing so:

Document Global Object

As mentioned before, the DOM tree must contain one root node. This node, for any instance of the DOM, is the document entry point. When in the browser, this entry point is exposed to the developer with the global object document. This object has various methods and properties to assist in a meaningful way. For example, given a standard HTML5 document:

<!DOCTYPE html><html><head>	<title>This is a page title</title></head><body>	<p id="mainText">    This is the page body		<span class="bolded">and it contains</span>		a lot of various content within    <span class="bolded">the DOM</span>	</p></body></html>

The document object has the ability to get the <body> node (document.body), the <head> node (document.head), and even the doctype (document.doctype).

A screenshot of the Chrome debugger console displaying those properties
Querying Elements

Besides containing static references to <body> and <head>, there is also a way to query any element by using CSS selectors. For example, if we wanted to get a reference to the single element with the id of mainText, we could use the CSS selector for an id, combined with the querySelector method on the document:

const mainTextElement = document.querySelector('#mainText');

The # in the #mainText is the CSS selector syntax for selecting an element based on its id. If you had a CSS selector of #testing, you'd be looking for an element with the following attribute value:


This method will return a reference to the element as rendered in the DOM. While we'll be covering more of what this reference is able to do later, for now we can execute this quick bit of code to show that it's the element we intended to query:

console.log(mainTextElement.innerHTML); // This will output the HTML that we used to write this element
A screenshot of the Chrome debugger running the above code

We also have the ability to gain a reference to many elements at once. Given the same HTML document as before, let's say we want to see how many elements have the bolded class applied to it. We're able to do so using the querySelectorAll method on the document.

const boldedElements = document.querySelectorAll('.bolded');console.log(boldedElements.length); // Will output 2console.log(boldedElements[0].innerHTML); // Will output the HTML for that element
A screenshot of Chrome running the above code

It's worth mentioning that the way querySelector works is not the same way that the browser checks a node against the CSS selector data when the browser "visits" that node. querySelector and querySelectorAll work from a more top-down perspective where it searches the elements one-by-one against the query. First, it finds the top-most layer of the CSS selector. Then it will move to the next item and so-on-so forth until it returns the expected results.

Element Base Class

While innerHTML has been used to demonstrate that the element that's gathered is in fact the element that was queried, there are many many more properties and methods that can be run on an element reference.

When an element is queried and returned, you're given a reference to that element through the Element base class. This class is what contains the properties and methods that you can use to access and modify the element's metadata.

For example, let's say that I wanted to see the width and height an element has when rendered on screen. Using the Element.prototype.getBoundingClientRect method, you can get all of that information and more:

const mainTextElement = document.querySelector('#mainText');console.log(mainTextElement.getBoundingClientRect());// Will output: DOMRect {x: 8, y: 16, width: 638, height: 18, top: 16, …}

While the explanation behind the Element.prototype is a lengthy one (an article on its own to be sure), suffice it to say that there's a base class for all element references found using querySelector. This base class contains a myriad of methods and properties. The .prototype loosely refers to those properties and methods in question.

This means that all queried elements will have their own getBoundingClientRect methods.


As covered earlier, elements are able to have attributes that will apply metadata to an element for the browser to utilize. However, what I may not have mentioned is that you're able to read and write that metadata, as well as applying new metadata, using JavaScript.

Let's take a slightly modified example from the correct tags section to demonstrate:

<div id="divToList">	<div>Bananas</div>	<div>Apples</div>	<div>Oranges</div></div>

We could update this list to include the roles and aria-labels in order to make this non-semantic HTML more relevant in terms of how it reflects its metadata to the browser.

This metadata that we place directly on the elements themselves are called attributes and are part of the HTML specification (also referred to as the HTML API in this document). This metadata can be accessed and modified from JavaScript by using the Element's getAttribute to read the key-value pairing and setAttribute to set the value to that attribute on an element.

Let's look at how we can set the role and aria-labels in the DOM using JavaScript:

const divToListEl = document.querySelector('#divToList');// Get the `role` attribute to demonstrate that there's no currently present roleconsole.log(divToListEl.getAttribute('role')); // `null`// Let's set a role that emulates a `list`// Set the value from the HTML API using the Element method `setAttribute`divToListEl.setAttribute('role', 'list');// And let's add an aria-label, for good measuredivToListEl.setAttribute('aria-label', 'My favorite fruits');// Get the value from the HTML API using the Element method `getAttribute`console.log(divToListEl.getAttribute('role')); // `'list'`// Using the CSS selector to get the children of the divsconst listItems = document.querySelectorAll('#divToList > *');// Now, for all of the items in that list, let's use an aria `role` to make them reflect as listitems in their metadata to the browserfor (var i = 0; i < listItems.length; i++) {	listItems[i].setAttribute('role', 'listitem');}

Once this is run, if you inspect the elements tab in your debugger, you should be left with HTML that looks like this:

<div id="divToList" role="list" aria-label="My favorite fruits">	<div role="listitem">Bananas</div>	<div role="listitem">Apples</div>	<div role="listitem">Oranges</div></div>

... which is significantly more accessible for users that utilize screen readers, as mentioned previously. You'll notice that despite not having any of the ARIA attributes prior, the setAttribute was able to implicitly create them with the newly placed values.


As mentioned in a prior section, elements also have properties and methods associated with the instance of the underlying base class. These properties are different from attributes as they are not part of the HTML specification. Instead, they're standardized JavaScript Element API additions. Some of these properties are able to be exposed to HTML and provide a two-way binding to-and-from the HTML API and the JavaScript Element API.

Unfortunately, for various historical reasons, the list of properties that support this bi-directional mapping between the Element API and the HTML API is sporadic and inconsistent. Some elements that support a mapping between the two APIs even only support uni-directional mapping where updating one will not update another.

This is a round-about way of saying, "It is confusing and complicated what properties have attribute bindings and which don't and why. It's okay if you don't get it right away". Even seasoned developers might not be aware of some of the limitations. That all said, let's continue on with some examples that do follow the bi-directional implicit API mapping to showcase how it works and learn more about properties.

For example, if you have the style attribute associated with an element you're working with, you're able to read the values of the element:

<!-- index.html --><div style="background-color: green; color: white; width: 200px; height: 400px;" id="greenEl">  This element is green</div>
// index.jsconst greenElement = document.querySelector('#greenEl');console.log(greenElement.style.backgroundColor); // 'green'
A screenshot of the element and the debugger console of the above code

Not only are you able to read the value in question, but you can write and edit them as well:

greenElement.style.backgroundColor = 'red';

Will turn the element's background color red, for example.

The element has now turned the background red

Somewhat silly, seeing as how the <div> is no longer green. 🤭


While attributes can be of great use to store data about an element, there's a limitation: Values are always stored as strings. This means that objects, arrays, and other non-string primitives must find a way to go to and from strings when being read and written.

While you've seen style attribute be read and written to by an object interface, if you inspect the element or use the getAttribute to access the attribute's HTML API value, you'll find that it's really a string with a pleasant API wrapped around it that lets you use an object to interface with the attribute value.

console.log(mainTextElement.getAttribute('style')); // This will return a string value, despite the API that lets you use an object to read and write

The reasoning behind this incongruity is due to the implicit mapping of the HTML API and the Element API, as mentioned at the start of the previous section. The limitations described here will also apply to the HTML API of those types of properties.

For example, we can use data attributes in order to read and write values via attributes to any given element.

<!-- index.html --><ul id="list" data-listitems="2">  <li>List item 1</li>  <li>List item 2</li></ul>
// index.jsconst listEl = document.querySelector('#list');console.log(listEl.dataset.listitems); // '2'listEl.dataset.listitems = 3;console.log(listEl.dataset.listitems); // '3'
Demonstrating that dataset values are able to be read and written

Note that I wrote the string '3' instead of the numerical value 3 in the code sample's outputs in the comments despite using the numerical 3 to set the value. This behavior is due to how default non-string values are saved to attributes.

By default, the primitive's toString will be called to store values.

element.dataset.userInfo = {name: "Tony"};console.log(element.dataset.userInfo); // "[object Object]"/** * "[object Object]" is because it's running `Object.prototype.toString()` * to convert the object to a string to store on the attribute */

If you're having a difficult time understanding why toString is bring run or what prototype is doing here, don't worry; you're in good company. The JavaScript prototype system is complex and can be difficult to follow.

For now, it will suffice just to know that you're only able to store strings in an element attribute.


Just as your browser uses the DOM to handle on-screen content visibility, your browser also utilizes the DOM for knowing how to handle user interactions. The way your browser handles user interaction is by listening for events that occur when the user takes action or when other noteworthy changes occur.

For example, say you have a form that includes a default <button> element. When that button is pressed, it fires a submit event that then bubbles up the DOM tree until it finds a <form> element. By default, this <form> element sends a GET HTML request to the server once it receives the submit event.

The bubble flow of the submit event

Bubbling, as shown here, is the default behavior of any given event. Its behavior is to move an event up the DOM tree to the nodes above it, moving from child to parent until it hits the root. Parent nodes can respond to these events as expected, stop their upward motion on the tree, and more.

Event Listening

Much like many of the other internal uses of the DOM discussed in this article, you're able to hook into this event system to handle user interaction yourself.

Let's look at an example of some code doing so:

<!DOCTYPE html><html><head>	<title>This is a page title</title></head><body>	<div id="red" style="height: 400px; width: 400px; background: red;">		<div id="blue" style="height: 300px; width: 300px; background: blue;">			<div id="green" style="height: 200px; width: 200px; background: green;"></div>		</div>	</div>	<script>		const redEl = document.querySelector('#red');		const blueEl = document.querySelector('#blue');		const greenEl = document.querySelector('#green');		redEl.addEventListener('click', () => {			console.log("A click handled on red using bubbling");			// This is set to false in order to use bubbling. We'll cover the `true` case later on		}, false);		blueEl.addEventListener('click', (event) => {			// Stop the click event from moving further up in the bubble			event.stopPropagation();			console.log("A click handled on blue using bubbling");		}, false);		greenEl.addEventListener('click', () => {			console.log("A click handled on green using bubbling");		}, false);	</script></body></html>

In this example, we're adding click listeners to three squares, each one smaller than their parent square. This allows us to see the effect of bubbling in our console. If you click on the red square, you'd expect the event to bubble up to <body>, but not down to #green. Likewise, if you clicked on the green square, you'd expect the event to bubble up to both #blue and #red as well as <body>.

However, as you can see, we're running stopPropagation on the event in the blue square. This will make the click event stop bubbling. This means that any click events that are called on #green will not make it to #red as they will be stopped at #blue.

The event bubbles upwards from green to blue but then is stopped by the stopPropagate call

You can see a running example of this here:


Bubbling isn't the only way events are able to move. Just as they can move up from the bottom, they can also move from the top down. This method of emitting events is known as capture mode.

Let's take the a look at some example code, with the same HTML as before but a new set of JavaScript:

redEl.addEventListener('click', () => {  console.log("A click handled on red using capturing");  // Setting true here will switch to capture mode}, true);blueEl.addEventListener('click', (event) => {  // Stop the click event from moving further down in the bubble  event.stopPropagation();  console.log("A click handled on blue using capturing");}, true);greenEl.addEventListener('click', () => {  console.log("A click handled on green using capturing");}, true);

As demonstrated by the code above, stopPropagation works as you might expect it to in capture mode as well!

stopPropagation works similarly to how it does in bubble mode, just that it stops events from moving down the tree

This means that when the user clicks on the red square, you'll see the following in your console:

"A click handled on red using capturing"
"A click handled on blue using capturing"

You won't see anything from the green square's eventListener, however.

You'll also notice that if you click on the green square, you'll never see the "A click handled on green using capture" message. This is due to the stopPropagation, as mentioned before. The click is being registered on the red square first and then stopped on the blue square.


This post is filled to the brim with information. 😵 Even I, the author, had a few amazing folks give it a re-read to confirm what I've written. Please don't be afraid or ashamed to re-read anything that might not have made sense or to revisit the post whenever a question arises. Hopefully, this has been a helpful exploration of the DOM and the ways you interact with it using code.

Please ask any questions or comments in our comments section and remember that we have a Discord for further conversation, including any questions!

Subscribe to our newsletter!

Subscribe to our newsletter to get updates on new content we create, events we have coming up, and more! We'll make sure not to spam you and provide good insights to the content we have.