4 Commits

Include renames

Author	SHA1	Message	Date
Andreas Reinhold / reiniandClaude Opus 5	3fb0a404db	Write the showcase examples' layout tags as an application does ... Plan step 38 review: nine sections' examples wrapped their components in <x-livewire-material::stack>, ::row and ::grid (148 tags) beside an unprefixed <x-button>, while bars, containment and the layout pages wrote <x-stack>. The code sample is what an application copies, and the example component rewrites only unprefixed tags to a configured prefix, so the namespaced ones taught a second form and escaped it. Every example now writes <x-stack>, <x-row> and <x-grid>; a test rejects a namespaced tag inside an example heredoc. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9	2026-09-15 06:11:08 +02:00
Andreas Reinhold / reiniandClaude Opus 5	79ca9a28b4	Stop drawing each section's title twice on its page ... Plan step 38 review: the frame's structural rule that kept a section's own <h2> for screen readers (Tailwind's [&>section>h2]:sr-only before, a showcase.css rule during the rewrite) was removed as dead weight once every section had a real heading, so each page drew its title twice, the <h1> and an identical headline under it. The <h2>s are md-visually-hidden again, the frame's comment says why, and the section page test asserts it. The Layout section's description said "window size classes"; M3's term is breakpoints. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9	2026-09-15 06:10:01 +02:00
Andreas Reinhold / reiniandClaude Sonnet 5	e1cdc52b48	Rewrite the showcase's Progress section without Tailwind ... Plan step 38: the "bind" example's wrapper div becomes <x-stack>/ <x-row>, and the one enlarged circular indicator moves to a data-md-showcase-progress-lg hook. Along the way, $examples changes from a ['Title' => [code, stack]] tuple back to the plain 'Title' => <<<'BLADE' every other section uses, with the row exceptions listed separately: the tuple's leading `[` broke Sections::index()'s regex, so every one of this section's examples was silently missing from the showcase search index. Fixing the shape recovers them — the Feature ShowcaseTest's search-index assertion count moves from 259 to 266. Every aria-label the Chromium ProgressTest reads off #progress (Linear, Circular, Circular wavy, Bound, the indeterminate variants) is unchanged. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9	2026-09-15 04:49:30 +02:00
Andreas Reinhold / reiniandClaude Opus 5	e57063b0f4	Add M3 Expressive progress indicators ... <x-progress>: linear or circular, flat or wavy, determinate or indeterminate, 4px or thick, in any colour role, following a server value through Livewire morphs or an Alpine expression in the browser. The first frame is server-rendered SVG; Compose Material 3's drawing and keyframes are ported to an Alpine component that animates only while something moves and the indicator is on screen. The previous commit already imported progress.js and included its showcase section without the files; this adds them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy	2026-09-13 07:05:52 +02:00