All components · Category: Navigation

Gliding tabs

Tabs with an indicator that glides under the selected one.

The indicator slides to the chosen tab and the panel fades in. It follows the tabs pattern from the accessibility guidelines: arrow keys, Home and End move the selection, and only the selected tab is in the tab order.

Try it

<tabs-glide>

ViewPreviewCodeCSS

tabs-glide: Tabs with an indicator that glides under the selected one. A picture of the real component, drawn from its own code. The controls change the picture and the code beside it; nothing here is sent or stored.

Generated from the component's manifest and the values above.

index.html

<tabs-glide locale="en"></tabs-glide>

<script>
  const element = document.querySelector("tabs-glide");
  element.addEventListener("tabs-glide:changed", (event) => {
    console.log(event.detail);
  });
</script>

Add the site's Taggor script once; the component appears when it loads.

taggor-component.js

const element = document.createElement("tabs-glide");
element.setAttribute("locale", "en");
element.addEventListener("tabs-glide:changed", (event) => {
  console.log(event.detail);
});
document.body.append(element);

Add the site's Taggor script once; the component appears when it loads.

TabsGlide.tsx

import { useEffect, useRef } from "react";

export function TabsGlide() {
  const ref = useRef<HTMLElement>(null);

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onChanged = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("tabs-glide:changed", onChanged);
    return () => {
      element.removeEventListener("tabs-glide:changed", onChanged);
    };
  }, []);

  return <tabs-glide ref={ref} locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 18 sends every prop of a custom element as a text attribute.
The event is heard with addEventListener, inside an effect.

TabsGlide.tsx

import { useEffect, useRef } from "react";

export function TabsGlide() {
  const ref = useRef<HTMLElement>(null);

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onChanged = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("tabs-glide:changed", onChanged);
    return () => {
      element.removeEventListener("tabs-glide:changed", onChanged);
    };
  }, []);

  return <tabs-glide ref={ref} locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 19 sets a property when the element already has it, an attribute otherwise.
The event is heard with addEventListener, inside an effect.

src/TabsGlide.vue

<script setup lang="ts">
function onChanged(event: Event) {
  console.log((event as CustomEvent).detail);
}
</script>

<template>
  <tabs-glide locale="en" @tabs-glide:changed="onChanged" />
</template>

vite.config.ts

import vue from "@vitejs/plugin-vue";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag === "tabs-glide",
        },
      },
    }),
  ],
});

Add the site's Taggor script once; the component appears when it loads.
vite.config.ts tells Vue that this tag is not a Vue component.

src/app/tabs-glide.component.ts

import { afterNextRender, Component, CUSTOM_ELEMENTS_SCHEMA, DestroyRef, ElementRef, inject } from "@angular/core";

@Component({
  selector: "app-tabs-glide",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <tabs-glide locale="en"></tabs-glide>
  `,
})
export class TabsGlideComponent {
  constructor() {
    const host = inject<ElementRef<HTMLElement>>(ElementRef);
    const element = () => host.nativeElement.querySelector("tabs-glide");
    const onChanged = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    afterNextRender(() => element()?.addEventListener("tabs-glide:changed", onChanged));
    inject(DestroyRef).onDestroy(() => element()?.removeEventListener("tabs-glide:changed", onChanged));
  }
}

Add the site's Taggor script once; the component appears when it loads.
The component declares CUSTOM_ELEMENTS_SCHEMA.
The event is heard with addEventListener, inside an effect.

src/TaggorComponent.svelte

<script>
  function onChanged(event) {
    console.log(event.detail);
  }
</script>

<tabs-glide locale="en" ontabs-glide:changed={onChanged}></tabs-glide>

Add the site's Taggor script once; the component appears when it loads.

How an agent gets a component like this onto a site:

taggor checktaggor publish

The CSS variables the component exposes, set the way a customer's page would.

styles.css

tabs-glide {
  --tg-accent: #6d28d9;
  --tg-radius: 16px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
tabs	list	none	The tabs, in order.
selected	number 0 to 4	0	The selected tab, from 0.
locale	pt-BR \| en	en	–

Prop names and descriptions are the component's own, in English, as its author wrote them.

Events

Events of the component, read from its manifest
Event	When it fires
changed	A tab was selected.

Build one with your agent

Paste this into your agent. It asks you before it signs in, pays or goes further than checking and publishing.

Build me a Taggor component like "Gliding tabs" (tabs-glide): Tabs with an indicator that glides under the selected one. Fetch https://taggor.dev/agent-setup/prompt.md and follow its instructions to set me up for Taggor. Ask me before you sign in, create an account, accept terms, pay for anything or type a secret. Check it with `taggor check` and publish it with `taggor publish`, and stop there. Do not promote it to production, attach it to a site, roll back anything or use --yes, --force or --force-drop-invalid unless I ask for exactly that in this conversation.

Related components

FAQ accordion<faq-accordion>
Mega menu<nav-mega-menu>
Breadcrumb trail<breadcrumb-trail>