# Hover Nav

> A pill of links where the highlight slides under the pointer and settles back on the current page. The ink version turns the text white right at its edges.

Navigation · nav, hover, pill, indicator · HTML, CSS, vanilla JS · no dependencies · updated 2026-10-16
Demo: https://kodza.dev/components/hover-nav/

## Files

The code below, served as files: byte for byte what the Kodza site copies (the CSS includes its theme guard).

- [`kodza-hover-nav.css`](https://kodza.dev/registry/hover-nav/kodza-hover-nav.css) · 6.2 KB
- [`kodza-hover-nav.js`](https://kodza.dev/registry/hover-nav/kodza-hover-nav.js) · 5.9 KB
- [`kodza-hover-nav.html`](https://kodza.dev/registry/hover-nav/kodza-hover-nav.html) · 0.6 KB · the markup, to adapt and paste into your page

**Can you run shell commands? Download the CSS and the JS, don't retype them.** Retyping costs thousands of tokens and can drop or change lines of the CSS. Put the files where your stack expects them (Use it says where: change the `-o` paths):

```bash
curl -fsSL --create-dirs -o kodza/kodza-hover-nav.css https://kodza.dev/registry/hover-nav/kodza-hover-nav.css
curl -fsSL --create-dirs -o kodza/kodza-hover-nav.js https://kodza.dev/registry/hover-nav/kodza-hover-nav.js
```

Then load the files from your page as Use it shows, instead of pasting the content. The HTML is the part you adapt (text, links, modifiers): paste it from the Code section. Copy the CSS and the JS from the Code section only if you can't run commands, exactly as they are. (Windows PowerShell: `curl.exe`.)

## API

- Root: `.kodza-hover-nav`
- Variables (set them on the root element itself: it declares its own defaults):
  - `--kz-hnav-bg: #ffffff`
  - `--kz-hnav-fg: #0a0a0a`
  - `--kz-hnav-muted: rgba(10, 10, 10, 0.58)`
  - `--kz-hnav-border: rgba(10, 10, 10, 0.1)`
  - `--kz-hnav-soft: rgba(10, 10, 10, 0.06)`
  - `--kz-hnav-ink: #0a0a0a`
  - `--kz-hnav-on-ink: #ffffff`
  - `--kz-hnav-duration: 0.45s`
  - `--kz-hnav-ease: cubic-bezier(0.22, 1, 0.36, 1)`
- Modifiers: `.kodza-hover-nav--ink`
- Lifecycle: `kodza:init` / `kodza:destroy` on `document`, with `{ detail: { root } }` to target a container.

## Dark mode

The values Kodza uses on a dark background (`#0a0a0a`). For a page that follows the system theme, add them after the component's CSS:

```css
@media (prefers-color-scheme: dark) {
  .kodza-hover-nav {
    --kz-hnav-bg: #161616;
    --kz-hnav-fg: #f2f2f0;
    --kz-hnav-muted: rgba(242, 242, 240, 0.6);
    --kz-hnav-border: rgba(255, 255, 255, 0.12);
    --kz-hnav-soft: rgba(255, 255, 255, 0.09);
    --kz-hnav-ink: #f2f2f0;
    --kz-hnav-on-ink: #0a0a0a;
  }
}
```

A site with its own theme switch puts the same rules under its dark selector instead (`[data-theme="dark"] .kodza-hover-nav { … }`); a single dark section, under that section's class.

## Use it

### Plain HTML page

- CSS: `kodza/kodza-hover-nav.css` next to the page (the Files commands as they are), linked in `<head>`: `<link rel="stylesheet" href="kodza/kodza-hover-nav.css">`. Without a shell, paste it in a `<style>` in `<head>` instead. It only touches `kodza-` classes.
- HTML: where the component goes. Paste it as many times as you need: instances never interfere.
- JS: `kodza/kodza-hover-nav.js`, loaded with `<script src="kodza/kodza-hover-nav.js" defer></script>` in `<head>`. Without a shell, paste it in a `<script>` before `</body>` (or in `<head>`: it waits for the page). One copy per page, whatever the number of instances.
- Restyle with the `--kz-…` variables, set on the component's root element itself (the root declares its own defaults, so a value on an ancestor is ignored), and with the modifiers / attributes listed under API.
- Font: it takes the page's own. The Kodza look is Geist: `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@400;500&display=swap">`.
- Content added later (AJAX navigation, a SPA route, a builder preview): start it with `document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: container } }))`; before removing it, the same call with `'kodza:destroy'` stops it and puts the original markup back.

### Claude artifact (claude.ai)

- Paste the CSS in a `<style>` and the JS in a `<script>` at the end, in the artifact itself: it loads stylesheets only from Google Fonts and scripts only from a few CDNs, so no `<link>` or `<script src>` to Kodza.
- Writing the artifact file with a shell? Insert the downloaded files (Files) with a command instead of retyping them: a line `KODZA-CSS` alone inside the `<style>`, `KODZA-JS` inside the `<script>`, then `sed -e '/^KODZA-CSS$/{r kodza/kodza-hover-nav.css' -e 'd' -e '}' -e '/^KODZA-JS$/{r kodza/kodza-hover-nav.js' -e 'd' -e '}' page.html > artifact.html`.
- Font: load Geist from Google Fonts (allowed): `<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Geist:wght@400;500;600;700&family=Geist+Mono:wght@400;500&display=swap">`.
- Dark mode: the viewer sets `data-theme="dark"` or `"light"` on `<html>`, or nothing when it follows the system. Write the Dark mode rules twice: inside `@media (prefers-color-scheme: dark)` with `:root:not([data-theme="light"])` in front of each selector, and with `:root[data-theme="dark"]` in front of each selector.

### WordPress

- HTML: a **Custom HTML** block (or a pattern / template part). WordPress keeps this markup as it is only for users allowed to post unfiltered HTML (Administrators; Super Admins on multisite): for anyone else it strips tags such as `<svg>`, `<input>` or `<dialog>`, so add it from the theme (a pattern or template part) instead.
- This one is inline (it flows like a word): pasted alone, many themes leave it at the edge of the page (block themes, and classic ones like Twenty Twenty-One or Blocksy), so put the Custom HTML block inside a **Group** block to line it up with the text.
- CSS and JS: the downloaded files go in the theme, under `wp-content/themes/<your-theme>/kodza/` (the child theme if there is one), enqueued from its functions.php (or a code-snippets plugin):
  ```php
  add_action('wp_enqueue_scripts', function () {
    $dir = get_stylesheet_directory() . '/kodza/';
    $uri = get_stylesheet_directory_uri() . '/kodza/';
    wp_enqueue_style('kodza-hover-nav', $uri . 'kodza-hover-nav.css', [], filemtime($dir . 'kodza-hover-nav.css'));
    wp_enqueue_script('kodza-hover-nav', $uri . 'kodza-hover-nav.js', [], filemtime($dir . 'kodza-hover-nav.js'), true);
  });
  ```
  Scoped to `kodza-` classes, the CSS never touches the theme. One copy of the JS, whatever the number of blocks.
- No access to the theme files? The CSS can also go, as it is, in **Appearance → Customize → Additional CSS** (classic theme) or **Styles → Additional CSS** in the Site Editor (block theme).
- Theme with AJAX page transitions: fire `kodza:init` on the new content after each swap (and `kodza:destroy` on the old one).
- Performance plugin (WP Rocket, LiteSpeed Cache, Perfmatters…) with **Delay JavaScript execution** turned on: add `kodza` to the scripts it must not delay. Otherwise the component waits for the visitor's first scroll, tap or mouse move, and that first click can be lost.
- Colours: by default, match the theme's palette. After the component's CSS, point these variables at the theme's colours, on the component root, Kodza's value as the fallback:
  `.kodza-hover-nav { --kz-hnav-fg: var(TEXT, #0a0a0a); --kz-hnav-bg: var(BACKGROUND, #ffffff); --kz-hnav-ink: var(ACCENT, #0a0a0a); --kz-hnav-on-ink: var(BACKGROUND, #ffffff); }`
  TEXT, BACKGROUND and ACCENT (the colour the theme fills its own buttons with) are the theme's own colour variables — block themes (theme.json, like Twenty Twenty-Five): `--wp--preset--color--contrast`, `--wp--preset--color--base`, `--wp--preset--color--contrast` (they fill their buttons with it; their accent-1… colours are decorative); Astra: `--ast-global-color-2`, `--ast-global-color-4`, `--ast-global-color-0`; Kadence: `--global-palette3`, `--global-palette9`, `--global-palette1`; GeneratePress: `--contrast`, `--base-3`, `--accent`; Blocksy: `--theme-palette-color-4`, `--theme-palette-color-8`, `--theme-palette-color-1`. Use only these names, and only if the site really has them (the theme's CSS, or Styles → Colors): the `--wp--preset--color--black`, `--white`, `--vivid-…` that WordPress adds everywhere are not the theme's palette. Another theme, or one without these variables (Hello Elementor, OceanWP): leave the variables alone, it keeps Kodza's monochrome; same when the developer asks for monochrome or the Kodza look. Leave the translucent greys (`rgba(10, 10, 10, …)`) as they are: they suit any light background. On a dark palette, set the other variables from Dark mode too.
- WordPress turns straight quotes and `--` into typographic ones in the text of a Custom HTML block (not inside `<code>` or `<pre>`).

#### With Elementor

- HTML: an **HTML** widget (Elementor shows it to administrators only). It keeps the code exactly as pasted, straight quotes included.
- CSS and JS: as above. Elementor's Site Settings → Theme Style styles every button, field, link and image of the page, components included; the theme guard at the end of the CSS keeps the component's buttons, fields and link colours as they are.
- The Elementor editor redraws each widget after the page has loaded: without the script below, the component stays still in the editor preview (the published page works). Add it once per site, in the footer like the component's script (`kodza/elementor-editor.js`, or a code-snippets plugin):

```js
// Kodza in the Elementor editor: the editor redraws each HTML widget after the page has loaded.
// Start Kodza in what it draws, stop it in what it replaces or removes. Once per site.
window.addEventListener('elementor/frontend/init', () => {
  if (!elementorFrontend.isEditMode()) return;
  class KodzaWidget extends elementorModules.frontend.handlers.Base {
    onInit() {
      super.onInit();
      this.kodza = [...this.$element[0].children];
      document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: this.$element[0] } }));
    }
    onDestroy() {
      super.onDestroy();
      this.kodza.forEach((root) => document.dispatchEvent(new CustomEvent('kodza:destroy', { detail: { root } })));
    }
  }
  elementorFrontend.elementsHandler.attachHandler('html', KodzaWidget);
});
```

- No child theme: everything can go in the HTML widget instead, `<style>` with the CSS, the HTML, then `<script>` with the JS. It works on the page and in the editor without the script above.

### Shopify

- Files: `assets/kodza-hover-nav.css` and `assets/kodza-hover-nav.js` (the Files commands with `-o assets/…`).
- In the section: `{{ 'kodza-hover-nav.css' | asset_url | stylesheet_tag }}` and `<script src="{{ 'kodza-hover-nav.js' | asset_url }}" defer></script>`, then the HTML.
- The theme editor re-renders sections: restart them with
  `document.addEventListener('shopify:section:load', (e) => document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root: e.target } })));`
  and the same with `shopify:section:unload` → `kodza:destroy`.

### React / Next.js

- Files, side by side (e.g. in `components/kodza/`): `HoverNav.tsx` (below), the CSS block under Code saved as `hover-nav.css` and the JS block as `hover-nav.js`, both as they are. The HTML block is already inside the component: skip it.
- Use it: `import { HoverNav } from '@/components/kodza/HoverNav';` then `<HoverNav />`. Props: `variant` ("ink", or several in an array), `vars` (the `--kz-…` variables listed under API, e.g. `vars={{ '--kz-hnav-bg': … }}`), `className`, `style` and the other props of its `<nav>` (`onClick`, `aria-…`).
- Next.js App Router: it is a Client Component already (`'use client'`). Pages Router: Next.js takes global CSS only in `pages/_app`, so move the `import './hover-nav.css'` line there.
- Safe under StrictMode, client-side navigation and prop changes: when a prop changes, the `key` gives React a fresh element, `kodza:destroy` stops the script on the old one and `kodza:init` starts it on the new one.

```tsx
'use client';
// Kodza — Hover Nav, for React. From https://kodza.dev/components/hover-nav/
// Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license
// Next to this file: hover-nav.css and hover-nav.js, the component's CSS and JS from Kodza, as they are.
// Yours to edit: the markup is plain JSX below.
// The script changes this markup once React has rendered it (it adds layers, splits text, moves
// nodes), so React must not patch it afterwards. When a prop changes, the key gives React a fresh
// element: kodza:destroy stops the script on the old one, kodza:init starts it on the new one.
import { useRef, useEffect, type ComponentPropsWithoutRef, type ComponentRef, type CSSProperties } from 'react';
import './hover-nav.css';

type Variant = "ink";

export type HoverNavProps = Omit<ComponentPropsWithoutRef<'nav'>, "children" | "variant" | "vars"> & {
  /** Modifier class(es): .kodza-hover-nav--ink */
  variant?: Variant | Variant[];
  /** Settings, as CSS variables on the root */
  vars?: {
    /** default: #ffffff */
    "--kz-hnav-bg"?: string | number;
    /** default: #0a0a0a */
    "--kz-hnav-fg"?: string | number;
    /** default: rgba(10, 10, 10, 0.58) */
    "--kz-hnav-muted"?: string | number;
    /** default: rgba(10, 10, 10, 0.1) */
    "--kz-hnav-border"?: string | number;
    /** default: rgba(10, 10, 10, 0.06) */
    "--kz-hnav-soft"?: string | number;
    /** default: #0a0a0a */
    "--kz-hnav-ink"?: string | number;
    /** default: #ffffff */
    "--kz-hnav-on-ink"?: string | number;
    /** default: 0.45s */
    "--kz-hnav-duration"?: string | number;
    /** default: cubic-bezier(0.22, 1, 0.36, 1) */
    "--kz-hnav-ease"?: string | number;
  };
  className?: string;
};

export function HoverNav({ variant, vars, className, style, ...rest }: HoverNavProps) {
  const ref = useRef<ComponentRef<'nav'>>(null);
  const classes = ["kodza-hover-nav", ...([] as string[]).concat(variant ?? []).map((v) => `kodza-hover-nav--${v}`), className].filter(Boolean).join(' ');
  // Everything the markup is made of: when it changes, React gets a fresh element (see the top)
  const key = JSON.stringify([classes, vars, style, rest]);

  // Starts the script on this element once React has rendered it, stops it when it goes
  useEffect(() => {
    const root = ref.current;
    let live = true;
    // @ts-ignore: a plain script, no types to find
    import('./hover-nav.js').then(() => {
      if (live) document.dispatchEvent(new CustomEvent('kodza:init', { detail: { root } }));
    });
    return () => {
      live = false;
      document.dispatchEvent(new CustomEvent('kodza:destroy', { detail: { root } }));
    };
  }, [key]);

  return (
    <nav aria-label="Main" key={key} {...rest} className={classes} style={{ ...vars, ...style } as CSSProperties} ref={ref}>
      <a className="kodza-hover-nav__link" href="#" aria-current="page">Home</a>
      {' '}
      <a className="kodza-hover-nav__link" href="#">Components</a>
      {' '}
      <a className="kodza-hover-nav__link" href="#">Pricing</a>
      {' '}
      <a className="kodza-hover-nav__link" href="#">Changelog</a>
    </nav>
  );
}
```

## Code

```html
<nav class="kodza-hover-nav" aria-label="Main">
  <a class="kodza-hover-nav__link" href="#" aria-current="page">Home</a>
  <a class="kodza-hover-nav__link" href="#">Components</a>
  <a class="kodza-hover-nav__link" href="#">Pricing</a>
  <a class="kodza-hover-nav__link" href="#">Changelog</a>
</nav>

<nav class="kodza-hover-nav kodza-hover-nav--ink" aria-label="Studio">
  <a class="kodza-hover-nav__link" href="#" aria-current="page">Work</a>
  <a class="kodza-hover-nav__link" href="#">Studio</a>
  <a class="kodza-hover-nav__link" href="#">Journal</a>
  <a class="kodza-hover-nav__link" href="#">Contact</a>
</nav>
```

```css
/* Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license */
/* Kodza — Hover Nav
   A pill of links where a soft highlight slides under the pointer (or the keyboard focus),
   then settles back on the current page. With --ink, the highlight is ink and the text it
   covers turns white exactly at its edges, even mid-slide. When the links outgrow the screen
   (a phone), they scroll sideways inside the pill.
   Everything is tuned with the --kz-hnav-* variables. */
.kodza-hover-nav {
  --kz-hnav-bg: #ffffff;
  --kz-hnav-fg: #0a0a0a;
  --kz-hnav-muted: rgba(10, 10, 10, 0.58);
  --kz-hnav-border: rgba(10, 10, 10, 0.1);
  --kz-hnav-soft: rgba(10, 10, 10, 0.06);
  --kz-hnav-ink: #0a0a0a;
  --kz-hnav-on-ink: #ffffff;
  --kz-hnav-duration: 0.45s;
  --kz-hnav-ease: cubic-bezier(0.22, 1, 0.36, 1);

  position: relative;
  display: inline-flex;
  box-sizing: border-box;
  max-width: 100%;
  padding: 4px;
  border-radius: 999px;
  background: var(--kz-hnav-bg);
  box-shadow: inset 0 0 0 1px var(--kz-hnav-border);
  isolation: isolate;
  /* More links than room (a phone): the pill keeps its width and its links scroll sideways */
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scrollbar-width: none;
}

.kodza-hover-nav::-webkit-scrollbar {
  display: none;
}

.kodza-hover-nav__link,
.kodza-hover-nav__ghost {
  display: inline-flex;
  align-items: center;
  height: 36px;
  padding: 0 16px;
  border-radius: 999px;
  font-size: 15px;
  font-weight: 500;
  white-space: nowrap;
}

.kodza-hover-nav__link {
  position: relative;
  z-index: 1;
  color: var(--kz-hnav-muted);
  text-decoration: none;
  transition: color 0.3s ease;
}

.kodza-hover-nav__link:hover,
.kodza-hover-nav__link[aria-current="page"] {
  color: var(--kz-hnav-fg);
}

.kodza-hover-nav__link:focus-visible {
  outline: 2px solid var(--kz-hnav-fg);
  outline-offset: -2px;
}

/* The highlight covers the whole nav (every link, scrolled out of sight or not) and is cut down
   to one link: only clip-path moves */
.kodza-hover-nav__highlight,
.kodza-hover-nav__mirror {
  position: absolute;
  inset: 0 auto 0 0;
  box-sizing: border-box;
  width: var(--kz-hl-w, 100%);
  border-radius: 999px;
  clip-path: inset(4px var(--kz-hl-r, 50%) 4px var(--kz-hl-l, 50%) round 999px);
  opacity: var(--kz-hl-on, 0);
  pointer-events: none;
}

.kodza-hover-nav__highlight {
  z-index: 0;
  background: var(--kz-hnav-soft);
}

.kodza-hover-nav.is-ready .kodza-hover-nav__highlight,
.kodza-hover-nav.is-ready .kodza-hover-nav__mirror {
  transition: clip-path var(--kz-hnav-duration) var(--kz-hnav-ease), opacity 0.25s ease;
}

/* --ink: an ink highlight, and a white copy of the links cut to the same shape */
.kodza-hover-nav--ink .kodza-hover-nav__highlight {
  background: var(--kz-hnav-ink);
}

.kodza-hover-nav__mirror {
  z-index: 2;
  display: flex;
  padding: 4px;
  color: var(--kz-hnav-on-ink);
}

@media (prefers-reduced-motion: reduce) {
  .kodza-hover-nav.is-ready .kodza-hover-nav__highlight,
  .kodza-hover-nav.is-ready .kodza-hover-nav__mirror,
  .kodza-hover-nav__link {
    transition-duration: 0.01ms !important;
  }
}

/* Theming example — on a dark background:
.dark-section .kodza-hover-nav {
  --kz-hnav-bg: #161616;
  --kz-hnav-fg: #f2f2f0;
  --kz-hnav-muted: rgba(242, 242, 240, 0.6);
  --kz-hnav-border: rgba(255, 255, 255, 0.12);
  --kz-hnav-soft: rgba(255, 255, 255, 0.09);
  --kz-hnav-ink: #f2f2f0;
  --kz-hnav-on-ink: #0a0a0a;
}
*/

/* kodza-guard 472370212bfd — generated by Kodza, do not edit.
   Theme guard: keeps a site's own CSS (WordPress themes, Bootstrap, CSS resets…) off this
   component. :not(#_) is always true and weighs as much as an id, so these lines win over
   theme rules made of classes and tags. Customise the component through its --kz-* variables. */

/* What the browser gives, where the component sets it only in some states: at the lowest weight, so its own rules below put it back */

:where(.kodza-hover-nav__link):not(#_) {
  outline: revert;
  outline-offset: revert;
}

/* What the browser gives, on everything the component leaves to it */

.kodza-hover-nav:not(#_) {
  border: revert;
  outline: revert;
  text-decoration: revert;
  transition: revert;
  list-style: revert;
  outline-offset: revert;
  appearance: revert;
  max-height: revert;
  color: revert;
  font-family: revert;
  font-size: revert;
  font-weight: revert;
  font-style: revert;
  line-height: revert;
  letter-spacing: revert;
  text-transform: revert;
  text-underline-offset: revert;
  text-align: revert;
  text-indent: revert;
  text-shadow: revert;
  vertical-align: revert;
}

.kodza-hover-nav__link:not(#_) {
  border: revert;
  margin: revert;
  list-style: revert;
  box-sizing: revert;
  float: revert;
  background-color: revert;
  background-image: revert;
  box-shadow: revert;
  appearance: revert;
  max-width: revert;
  max-height: revert;
  font-family: revert;
  font-style: revert;
  line-height: revert;
  letter-spacing: revert;
  text-transform: revert;
  text-underline-offset: revert;
  text-align: revert;
  text-indent: revert;
  text-shadow: revert;
  vertical-align: revert;
}

.kodza-hover-nav__ghost:not(#_) {
  box-sizing: revert;
}

/* The component's own rules, one step stronger: real buttons and fields, what it sets on tags themes style (links, lists, headings, images…), and the root width (a theme may narrow it, never widen it) */

.kodza-hover-nav:not(#_) {
  position: relative;
  display: inline-flex;
  box-sizing: border-box;
  padding: 4px;
  border-radius: 999px;
  background: var(--kz-hnav-bg);
  box-shadow: inset 0 0 0 1px var(--kz-hnav-border);
}

.kodza-hover-nav__link:not(#_) {
  display: inline-flex;
  padding: 0 16px;
  border-radius: 999px;
  font-size: 15px;
  font-weight: 500;
}

.kodza-hover-nav__link:not(#_) {
  position: relative;
  color: var(--kz-hnav-muted);
  text-decoration: none;
  transition: color 0.3s ease;
}

.kodza-hover-nav__link:hover:not(#_),
.kodza-hover-nav__link[aria-current="page"]:not(#_) {
  color: var(--kz-hnav-fg);
}

.kodza-hover-nav__link:focus-visible:not(#_) {
  outline: 2px solid var(--kz-hnav-fg);
  outline-offset: -2px;
}

@media (prefers-reduced-motion: reduce) {
  .kodza-hover-nav__link:not(#_) {
    transition-duration: 0.01ms !important;
  }
}
```

```js
// Kodza License: free to use, client work included. Not to resell or redistribute, ported or not: https://kodza.dev/docs/#print-license
// Kodza — Hover Nav
// Adds the highlight (and, with --ink, the white copy of the links), moves it to the link
// under the pointer or the keyboard focus, and brings it back to the current page.
(() => {
  const SELECTOR = '.kodza-hover-nav';
  // One instance. Everything it starts is tied to `signal`, so kodza:destroy stops it all
  function mount(root, signal) {
    const links = [...root.querySelectorAll('.kodza-hover-nav__link')];
    if (!links.length) return;

    const highlight = document.createElement('span');
    highlight.className = 'kodza-hover-nav__highlight';
    highlight.setAttribute('aria-hidden', 'true');
    root.prepend(highlight);

    if (root.classList.contains('kodza-hover-nav--ink')) {
      const mirror = document.createElement('span');
      mirror.className = 'kodza-hover-nav__mirror';
      mirror.setAttribute('aria-hidden', 'true');
      mirror.append(...links.map((link) => {
        const ghost = document.createElement('span');
        ghost.className = 'kodza-hover-nav__ghost';
        ghost.textContent = link.textContent;
        return ghost;
      }));
      root.append(mirror);
    }

    const current = () => links.find((link) => link.getAttribute('aria-current') === 'page');

    const reduceMotion = window.matchMedia('(prefers-reduced-motion: reduce)').matches;
    const padding = () => parseFloat(getComputedStyle(root).paddingRight) || 0;
    // When the links scroll, the highlight spans all of them (read from the last link, not
    // scrollWidth, which a highlight still at its old width would inflate); otherwise the pill
    const span = () => {
      const last = links[links.length - 1];
      const end = last.offsetLeft + last.offsetWidth + padding();
      return end > root.clientWidth + 1 ? end : 0;
    };
    const move = (link) => {
      if (!link) {
        root.style.setProperty('--kz-hl-on', 0);
        return;
      }
      const scrolling = span();
      const width = scrolling || root.clientWidth;
      if (scrolling) root.style.setProperty('--kz-hl-w', `${width}px`);
      else root.style.removeProperty('--kz-hl-w');
      root.style.setProperty('--kz-hl-l', `${link.offsetLeft}px`);
      root.style.setProperty('--kz-hl-r', `${width - link.offsetLeft - link.offsetWidth}px`);
      root.style.setProperty('--kz-hl-on', 1);
    };
    const rest = () => move(current());

    // A link reached by the keyboard scrolls fully into the pill (the browser stops at half)
    const reveal = (link) => {
      const left = link.offsetLeft - padding();
      const right = link.offsetLeft + link.offsetWidth + padding() - root.clientWidth;
      const behavior = reduceMotion ? 'auto' : 'smooth';
      if (root.scrollLeft > left) root.scrollTo({ left, behavior });
      else if (root.scrollLeft < right) root.scrollTo({ left: right, behavior });
    };

    links.forEach((link) => {
      link.addEventListener('pointerenter', () => move(link), { signal });
      link.addEventListener('focus', () => {
        move(link);
        reveal(link);
      }, { signal });
      // On a one-page site (#anchors), the clicked link becomes the current one
      link.addEventListener('click', () => {
        if (!link.getAttribute('href')?.startsWith('#')) return;
        links.forEach((other) => other.toggleAttribute('aria-current', other === link));
        link.setAttribute('aria-current', 'page');
      }, { signal });
    });
    root.addEventListener('pointerleave', rest, { signal });
    root.addEventListener('focusout', (event) => {
      if (!root.contains(event.relatedTarget)) rest();
    }, { signal });

    rest();
    // Its first place is computed now, before is-ready turns the slide on: it must not slide in
    void getComputedStyle(highlight).clipPath;
    // Links scrolling in a narrow pill: the current page starts in view
    const here = current();
    if (here && root.scrollWidth > root.clientWidth) root.scrollLeft = here.offsetLeft + here.offsetWidth / 2 - root.clientWidth / 2;
    const observer = new ResizeObserver(() => move(links.find((link) => link.matches(':hover, :focus')) || current()));
    observer.observe(root);
    signal.addEventListener('abort', () => observer.disconnect());
    document.fonts?.ready.then(() => !signal.aborted && rest());
  }

  // Kodza lifecycle, the same in every component: `kodza:init` starts the instances inside
  // event.detail.root (the whole page by default), `kodza:destroy` stops them and puts their
  // markup back. For themes and apps that swap content without a page load.
  const instances = new WeakMap();
  const find = (scope = document) => [scope, ...scope.querySelectorAll(SELECTOR)].filter((el) => el.matches?.(SELECTOR));
  const init = (scope) => find(scope).forEach((root) => {
    if (root.classList.contains('is-ready')) return; // already running, maybe from another copy of this script
    const controller = new AbortController();
    instances.set(root, { controller, html: root.innerHTML, attrs: [...root.attributes].map((a) => [a.name, a.value]) });
    mount(root, controller.signal);
    root.classList.add('is-ready');
  });
  const destroy = (scope) => find(scope).forEach((root) => {
    const instance = instances.get(root);
    if (!instance) return;
    instances.delete(root);
    instance.controller.abort();
    [...root.attributes].forEach((a) => root.removeAttribute(a.name));
    instance.attrs.forEach(([name, value]) => root.setAttribute(name, value));
    root.innerHTML = instance.html;
  });
  document.addEventListener('kodza:init', (event) => init(event.detail?.root));
  document.addEventListener('kodza:destroy', (event) => destroy(event.detail?.root));
  init();
  // Loaded in <head>, the script runs before the markup exists: once more when it is parsed
  if (document.readyState === 'loading') document.addEventListener('DOMContentLoaded', () => init(), { once: true });
})();
```

Free to use, from Kodza (https://kodza.dev).