Absolute vs relative XPath

The difference in one table

Examples

Absolute: /html/body/main/form/button selects a button through a root-based chain. A new wrapper between main and form can invalidate that chain.

Relative: .//button evaluated from a selected form looks through that form's descendants. Adding a wrapper elsewhere on the page does not affect that scope. Choose a stable attribute if the form contains several buttons.

The interview trap: Selenium discussions often call //button “relative XPath” because it avoids the full tag chain. In XPath grammar, a leading // is root-based shorthand. Use .//button when you mean descendants of the current element.

How to answer in an interview

An absolute XPath starts from the document root, while a relative XPath is evaluated from a context node. Long positional root paths often break when layout wrappers change, so I prefer stable attributes and deliberate scoping. From an existing form, .//button stays within that form's descendants. A leading // is commonly called relative in interviews, but its formal XPath meaning is root-based.

Common confusion

Short does not automatically mean robust: a text-only locator can break with translation, and generated IDs may change. Validate the match count and intended context rather than choosing a path only because it has fewer slashes. The runnable example below tests path semantics on a small document, not a real browser application.

Likely follow-up: Can relative paths use positions? Yes. Relative and absolute describe the starting context, not whether predicates or numeric positions appear.

Try the context difference locally

This JavaScript example uses Node and the jsdom development dependency installed by this repository. Run it as an ES module from the repository root. It was executed locally with assertions; it demonstrates XPath evaluation rather than Selenium execution.

import assert from 'node:assert/strict';
import { JSDOM } from 'jsdom';

const { window } = new JSDOM(`
  <main>
    <form id="checkout"><button>Pay</button></form>
    <button>Help</button>
  </main>
`);
const { document, XPathResult } = window;
const form = document.getElementById('checkout');
const count = (path, context) => document.evaluate(
  path, context, null, XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null
).snapshotLength;

assert.equal(count('/html/body/main/form/button', document), 1);
assert.equal(count('.//button', form), 1);
assert.equal(count('//button', form), 2);
console.log('XPath assertions passed');

The final assertion is the important one: changing the context node to the form does not make a leading // stay inside the form.