Tabs
Tabbed navigation — a compound panel-switching primitive, or a standalone bar whose active marker slides between tabs.
Preview
Make changes to your account here. Use the arrow keys to move between tabs.
Change your password here. Focus follows the selected tab automatically.
Controls
Device view renders in an isolated frame so real responsive breakpoints apply. Switch to Full for overflowing popovers.
Installation
php artisan ui:add tabs
Behavior layer (Alpine)
This component installs a self-registering Alpine module to
resources/js/ui/tabs.js. Import the behavior layer once
from your bundle so it loads (it hooks alpine:init):
import './tabs.js';
Registry contract
Install confidence
php artisan ui:add tabs
writes only the generated targets below. The CLI validates each file hash before writing and
prompts before replacing local changes unless --force is used.
- Version
- 1.2.0
- License
- open
- Stability
- stable
- Contract
- v2
- Foundation
- ≥ 1.0.0
| Type | Generated target |
|---|---|
| blade | resources/views/components/ui/tabs.blade.php |
| blade | resources/views/components/ui/tabs/list.blade.php |
| blade | resources/views/components/ui/tabs/trigger.blade.php |
| blade | resources/views/components/ui/tabs/content.blade.php |
| js | resources/js/ui/tabs.js |
Registry dependencies
None.
Package dependencies
composer: jml/brok:^1.0
npm: alpinejs
Guidance
Peer-section tabsSwitch between a few substantial peer sections.
Use when
- Use for a few peer sections with relatively long content and likely back-and-forth switching. Do not use for many short sections where accordions or a list would fit better.
Avoid when
- Best for a few longer peer sections when users are likely to switch between them.
- Task length
- short
- Interaction cost
- medium
- Interruptiveness
- none
- Input precision
- none
- Mobile / touch risk
- medium
- Accessibility risk
- high
- Needs background context
- Yes
- Comparison needed
- Yes
Preferred alternatives
- Accordion for many short secondary sections
- Dedicated pages for distinct destinations
Anti-patterns
- Using tabs for sequential progress
- Creating too many tabs to scan
API
manifest knowledge + registry-derived coverageProps
| Prop | Type / values | Default | Description |
|---|---|---|---|
| default | string | first trigger value | Initial active tab value. |
| disabled | false|true | false | Documented catalog control used by the preview workbench. |
| orientation | string | horizontal | Declared by @props in the registry Blade source. |
| variant | string | pills | Declared by @props in the registry Blade source. |
| fullWidth | bool | false | Declared by @props in the registry Blade source. |
| value | mixed | required | Declared by @props in the registry Blade source. |
Slots
default— Compose tabs.list, tabs.trigger, and tabs.content children.x-ui.tabs.list— Installed subcomponent from the registry item.x-ui.tabs.trigger— Installed subcomponent from the registry item.x-ui.tabs.content— Installed subcomponent from the registry item.
Data slots
tabs
tabs-content
tabs-list
tabs-trigger
Capabilities
Behavior
- Uses server-rendered Blade and semantic HTML.
- Uses ARIA tab roles and arrow-key navigation with selected panel syncing.
- Installs a JavaScript behavior module when the registry item includes resources/js/ui files.
- Declares registry capability flags: a11y, interactive, responsive, rtl, darkMode, localized.
Usage
<x-ui.tabs default="account" class="w-full max-w-md">
<x-ui.tabs.list>
<x-ui.tabs.trigger value="account">{{ __('Account') }}</x-ui.tabs.trigger>
<x-ui.tabs.trigger value="password">{{ __('Password') }}</x-ui.tabs.trigger>
</x-ui.tabs.list>
<x-ui.tabs.content value="account">
<p class="text-muted-foreground">{{ __('Make changes to your account here. Use the arrow keys to move between tabs.') }}</p>
</x-ui.tabs.content>
<x-ui.tabs.content value="password">
<p class="text-muted-foreground">{{ __('Change your password here. Focus follows the selected tab automatically.') }}</p>
</x-ui.tabs.content>
</x-ui.tabs>
Accessibility & localization
data-slot
Keyboard focus-visible
Localized labels
- Accessibility target: wcag-2.2-aa-target.
- Uses semantic HTML and a stable
data-slotattribute for styling/scripting hooks. - Focus-visible rings use the
ringtoken so keyboard focus is always visible. - Disabled and invalid states are conveyed to assistive tech, not by color alone.
- Targets WCAG 2.2 AA; verify contrast in light, dark, admin and customer surfaces above.
- Labels go through
__()and the component uses logical properties (ms-*,text-start,start-*) so it mirrors correctly — flip the preview to RTL to confirm.
Source
The exact, editable file ui:add writes
into your app — copy it or own the whole thing. Previews
render this same code; there are no preview-only components.
Changelog
Current version: v1.2.0. See the site changelog for the full release history.