Skip to content
UI Brok

Loading…

No results

Browse catalog

Chat Thread

A vertical stack of chat bubbles composing a back-and-forth conversation.

Preview

You
Is the Q3 launch still on track?
Support
Yes — the rollout is staged behind a flag and we are on schedule for the end of the quarter.

Controls

Theme
Surface
Direction
Viewport

Device view renders in an isolated frame so real responsive breakpoints apply. Switch to Full for overflowing popovers.

Installation

terminal 
php artisan ui:add chat-thread

Registry contract

Install confidence

php artisan ui:add chat-thread 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
2.0.0
License
open
Stability
stable
Contract
v2
Foundation
≥ 1.0.0
Type Generated target
blade resources/views/components/ui/chat-thread.blade.php

Registry dependencies

chat-bubble

Package dependencies

composer: jml/brok:^1.0

Guidance

Card and content widget

Present a self-contained content object with local context.

Use when

  • Use when self-contained content objects benefit from a recognizable card-like presentation with local actions or metadata. Do not use card widgets where a simpler list, table, or plain text block would make comparison faster.

Avoid when

  • Avoid using chat-thread as a default simply because it is available in the library. Choose it only when its interaction cost, visibility, and behavior match the job to be done.
Task length
short
Interaction cost
medium
Interruptiveness
none
Input precision
none
Mobile / touch risk
medium
Accessibility risk
medium
Needs background context
No
Comparison needed
Yes

Preferred alternatives

  • List for compact scanning
  • Table for exact comparison

Anti-patterns

  • Using cards for dense cross-item comparison
Related: chat-bubble

API

manifest knowledge + registry-derived coverage

Props

Prop Type / values Default Description
messages array|null null Conversation turns with role, name, avatar, and content keys.

Slots

Components use the default Blade slot unless a documented subcomponent is installed by the registry item.

Data slots

chat-thread

Capabilities

wcag-2.2-aa-target responsive rtl darkMode localized

Behavior

  • Uses server-rendered Blade and semantic HTML.
  • Composes chat-bubble for each turn and provides a small fallback conversation when no messages are supplied.
  • Declares registry capability flags: a11y, responsive, rtl, darkMode, localized.

Usage

previews.components.chat-thread.default.blade.php Blade 
<x-ui.chat-thread class="mx-auto w-full max-w-md" />

Accessibility & localization

WCAG 2.2 AA RTL-ready data-slot Keyboard focus-visible Localized labels
  • Accessibility target: wcag-2.2-aa-target.
  • Uses semantic HTML and a stable data-slot attribute for styling/scripting hooks.
  • Focus-visible rings use the ring token 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: v2.0.0. See the site changelog for the full release history.