Files
livewire-material/resources/views/showcase/layout/supporting-pane.blade.php
T
Andreas Reinhold / reiniandClaude Opus 5 fb7007c976
tests / feature (8.4) (push) Successful in 2m0s
tests / feature (8.5) (push) Successful in 2m0s
tests / browser (chrome, chromium) (push) Failing after 8m3s
tests / browser (firefox, firefox) (push) Failing after 12m58s
tests / browser (safari, webkit) (push) Failing after 13m8s
Take Tailwind out of the package, and its detection out of the guard
Tailwind left the stack in 2.0.0, but the package still carried about 330
mentions of it. What the guard's Tailwind detection protected — a class
that compiles to nothing — is now protected by a check that does not care
where a dead class came from.

DesignGuard: about 500 lines of Tailwind tables, scales, palettes and
"2.0.0 replacement" hints give way to one check — a class a view or PHP
file writes that neither the application's stylesheets nor the package's
own declare. It catches a utility of any framework, a typo and a class
whose rules were deleted alike, so it also found two classes ReStride
draws nothing with. A stylesheet has to be in reach for it: the `.css`
files among the scanned paths, or what the `missingStylesheets()` entry
imports. The class reader no longer mistakes an array index for a class
list (`$block['base']`), and it reads the array a class helper is given,
where it read nothing before.

The package's own three Tailwind self-guards go with it. Only their one
unique check stays, as a test of its own: every `matchMedia` width in
resources/js is an M3 breakpoint.

The pagination views are `material.blade.php` and
`simple-material.blade.php`; only Laravel's and Livewire's default theme
names ever made them `tailwind`. The provider sets `Paginator`'s default
views and switches `livewire.pagination_theme` to `material` when it is
still Livewire's own default, so no application can forget the config; a
theme an application chose, and a component's own `$paginationTheme` or
`paginationView()`, still win.

The rest is prose: the layer-order guidance for an application that still
builds Tailwind, the Tailwind wording in the README, the Boost guidelines
and the development skill, and about 25 "this used to be a Tailwind
utility" comments, along with every "plan step NN" pointer into a
gitignored folder. The reset keeps its credit, and NOTICE now carries it
too.

Feature suite 1159 passed, Chrome browser suite 299 passed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-17 21:07:39 +02:00

55 lines
2.9 KiB
PHP

{{-- The supporting-pane canonical layout on a page of its own: the same working demo the
Layout section's Overview linked from its own navigation, built on the real
<x-supporting-pane>, with the live breakpoint readout the Overview page has. --}}
@extends('livewire-material::showcase.layout')
@php
$code = <<<'BLADE'
<x-supporting-pane label="Comments" compact="sheet">
<x-slot:main>
<x-surface level="surface" corner="lg" style="overflow: clip">
<x-pane title="Trip proposal" subtitle="Draft · edited today" heading="h3" :sticky="false">
<x-stack gap="space200" style="padding-block-end: var(--md-sys-measurement-space300)">
<p class="md-type-body-lg">Three days by the lake in June: the train on Friday morning, two nights at the harbour, and a walk round the old town on Sunday before the train home.</p>
<p class="md-type-body-lg">From 840px the comments sit beside the proposal, 360px wide (412px from 1200px). Below it they are a bottom sheet docked to the window: press its handle to read them.</p>
</x-stack>
</x-pane>
</x-surface>
</x-slot:main>
<x-slot:supporting>
<x-surface level="surface-container-low" corner="lg" padding="space200">
<x-list label="Comments">
<x-list-item title="Anna Müller" description="Friday works for me." avatar="AM" />
<x-list-item title="Ben Keller" description="Can we stay a third night?" avatar="BK" />
</x-list>
</x-surface>
</x-slot:supporting>
</x-supporting-pane>
BLADE;
@endphp
@section('content')
<x-livewire-material::pane width="wide" data-md-showcase-page>
<x-livewire-material::stack gap="space300">
<x-livewire-material::stack as="header" gap="space50">
<p class="md-type-label-lg md-ink-variant">Foundations</p>
<h1 class="md-type-headline-lg">Layout</h1>
</x-livewire-material::stack>
<x-livewire-material::section-nav :items="array_values(\NoNameWeb\LivewireMaterial\Showcase\Sections::layoutPages())" label="Layout pages" />
<x-showcase::breakpoint-readout />
<p class="md-type-body-md md-ink-variant">
M3's supporting pane: a focus pane, and beside it what only means something in relation to it the
comments on a document, the details of a video. Below 840px it moves under the focus pane or into a
bottom sheet; from 840px it sits beside it, a fixed 360px (412px from 1200px).
</p>
<x-showcase::example title="Supporting pane" :code="$code" stack />
</x-livewire-material::stack>
</x-livewire-material::pane>
@endsection