Course contentsShow
← Web Development
Lesson 705 of 2,98212. The Document Object ModelFree lesson

parentNode and parentElement

Accessing an element's parent in the DOM tree and understanding the difference between these properties.

parentNode and parentElement

You'll learn how to access an element's parent container and understand when these two properties differ.

When navigating the DOM tree, you often need to move "up" from a child element to its parent. JavaScript provides two properties for this: parentNode and parentElement. They sound similar—and usually are the same—but there's a subtle difference worth knowing.

The Core Idea

Both properties let you access the immediate parent of a DOM node. Think of it like asking "Who is this element's container?" Most of the time, they return identical results:

const child = document.querySelector('.child');
const parent1 = child.parentNode;
const parent2 = child.parentElement;
// Usually parent1 === parent2

The Key Difference

The distinction appears at the very top of the tree:

  • parentNode works on any node type and returns the parent node (which might be a Document node)
  • parentElement specifically returns an Element parent, or null if the parent isn't an element

For example, document.documentElement.parentNode returns the Document object, but document.documentElement.parentElement returns null because the Document isn't an element.

Practical Usage

In everyday DOM manipulation with regular HTML elements, both work identically:

const button = document.querySelector('button');
const container = button.parentElement; // Gets the parent element

For consistency and clarity when working with typical elements, parentElement is slightly more precise since you know you're getting an element (or null).

Key Takeaway: parentNode and parentElement both access an element's parent container; use parentElement for regular HTML elements, knowing it guarantees an element-or-null return value, while parentNode is more general-purpose.