Toolbar

Overview

The Toolbar component is a core building block of the Byteion design system, providing a robust, accessibility-compliant interface for its specific UI capabilities.

Why this exists

This component provides a reusable, accessible primitive for toolbar use cases within the Byteion design system.

Mental model

When to use

When not to use

Basic example

The following example demonstrates standard usage, fully compliant with Byteion's token-first approach.

import {
  Button,
  Input,
  Toolbar,
  ToolbarGroup,
  ToolbarSeparator,
  ToolbarTitle,
} from '@byteion/react';

export default function ToolbarDemo() {
  return (
    <Toolbar className="w-full">
      <ToolbarTitle>Orders</ToolbarTitle>
      <ToolbarGroup>
        <Input placeholder="Search orders" className="h-9 max-w-48" />
        <Button variant="outline" tone="neutral" size="sm">Filter</Button>
      </ToolbarGroup>
      <ToolbarSeparator />
      <ToolbarGroup>
        <Button size="sm">Create</Button>
      </ToolbarGroup>
    </Toolbar>
  );
}

<script setup lang="ts">
import { Button, Input, Toolbar } from '@byteion/vue';
</script>

<template>
  <Toolbar class="w-full">
    <div data-bi-toolbar-title class="mr-auto text-sm font-medium text-foreground">Orders</div>
    <div data-bi-toolbar-group class="flex items-center gap-2">
      <Input placeholder="Search orders" class="h-9 max-w-48" />
      <Button variant="outline" tone="neutral" size="sm">Filter</Button>
    </div>
    <div role="separator" aria-orientation="vertical" data-bi-toolbar-separator class="mx-1 h-6 w-px bg-border" />
    <div data-bi-toolbar-group class="flex items-center gap-2">
      <Button size="sm">Create</Button>
    </div>
  </Toolbar>
</template>

States

This component reacts seamlessly to the following interaction and data states:

• default — Resting appearance before interaction.
• active — Currently selected or in use.

Anatomy

Usage guidelines

• Follow the design system tokens.
• Maintain consistent spacing.

Do and Don't

Accessibility

This component follows standard ARIA patterns for its role. Keyboard interaction matches the native HTML element behavior.

Customization

Override visual appearance by modifying variables.css or Tailwind utility classes.

import { cva, cn, type VariantProps } from '@byteion/react';

const myToolbar = cva('base classes…', {
 variants: {
  accent: { soft:'border-primary-200', loud:'border-primary-500' },
 },
 defaultVariants: { accent:'soft' },
});

type Props = React.HTMLAttributes<HTMLDivElement> & VariantProps<typeof myToolbar>;

<script setup lang="ts">
import { computed, useAttrs } from 'vue';
import { cva, type VariantProps } from '@byteion/vue';

interface Props { accent?:'soft' |'loud' }
const props = withDefaults(defineProps<Props>(), { accent:'soft' });
const attrs = useAttrs();

const myToolbar = cva('base classes…', {
  variants: { accent: { soft:'border-primary-200', loud:'border-primary-500' } },
});

const cls = computed(() => myToolbar({ accent: props.accent, class: attrs.class as string | undefined }));
</script>

Runtime events

Byteion keeps framework APIs idiomatic: HTML uses DOM custom events, React uses callback props, and Vue uses emitted events / v-model updates.

Remote / AJAX

API Reference

No custom data attributes required. Uses standard HTML attributes.

export interface ToolbarProps extends HTMLAttributes<HTMLDivElement> {
  density?: 'comfortable' | 'compact';
}

Developer tips

Common mistakes

Production usage tips

Premium examples

Advanced patterns available in Byteion Pro:

Related components

• Filter Bar
• Data Table
• View Switcher