Andreas Reinhold / reiniandClaude Opus 5
247c596c3a
An over-engineering audit of the whole tree, applied in five reviewed batches. Behaviour stays the same except where UPGRADE.md says otherwise. PHP: the showcase and error-page stylesheets are prebuilt into resources/dist by bin/stylesheets.mjs, through Vite's own postcss-import (first occurrence kept, the order an application's build gives), instead of Stylesheets::bundle() inlining imports on every request; only the import walk DesignGuard needs stays. SchemeStylesheet::withProfiles() replaces three copies of the scheme-plus-profiles loop, material:scheme leaves spec and contrast checks to the node script that already made them, and the error page's scheme cache, the hashed view namespace, the translations path with no lang/ folder and DesignGuard's 1.x-name hints are gone. JS: the androidx shape port progress.js and both bin scripts each carried lives once in resources/js/shapes.js (the generated SVGs are unchanged); util.js holds ringIndex(), ms(), reopenGuard() and remember(), which were written out several times; listeners are released through AbortController; tooltip.js's hoverPopover() serves the rich tooltip too. CSS: every rule for an element inside the navigation rail queries `--md-navigation-rail-value` instead of repeating the seven collapsed conditions under five media branches; badge, alert, progress, slider and button read one non-inheriting colour-role table (components/color.css); the dialog chrome, the submenu's popover chrome, the chip's state layer and touch target, and the visually-hidden inputs use the shared rules they copied; foundation/tokens.css is folded into foundation.css. Views: Support\Field and Support\Link replace the error-key, bound-value and link-attribute blocks copied into the fields and link components; the timepicker period group, the menu filter and the showcase head are partials; the datepicker's steppers and entry fields are loops; component docblocks no longer restate SKILL.md. Tests and tooling: one dataset-driven ComponentStylesheetsTest replaces four per-group files, DesignGuardTest and the layout-component tests use datasets, browser tests share one ready() helper, CSS parsing lives in ComponentStylesheet alone. docs/audits and the finding IDs citing it are removed, as are pestphp/pest-plugin-laravel, the unused composer scripts and check:font; the lint job runs in the feature job, which now installs node packages so the prebuilt-stylesheet staleness test runs in CI. Feature suite 1177 passed, Chrome browser suite 299 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
47 lines
2.4 KiB
CSS
47 lines
2.4 KiB
CSS
/*
|
|
* Livewire Material — the foundation, the one stylesheet every application imports, first:
|
|
*
|
|
* @import '../../vendor/nonameweb/livewire-material/resources/css/foundation.css';
|
|
* @import './material-scheme.css';
|
|
*
|
|
* Plain CSS, no build step of its own: an application's bundler (Vite) inlines the imports, and a
|
|
* browser could read the files as they are.
|
|
*
|
|
* Every rule of the package sits in a sub-layer of `material`, in this order, lowest first:
|
|
*
|
|
* material.reset foundation/reset.css — the browser's defaults taken back
|
|
* material.tokens tokens/*.css, imported here directly — every `--md-sys-*` and
|
|
* `--md-ref-*` property
|
|
* material.base foundation/base.css, foundation/interaction.css — the page, the font
|
|
* face, and md-state-layer, md-focus-ring, md-touch-target, md-link
|
|
* material.layout the layout components: scaffold, panes, the canonical layouts
|
|
* material.components the components
|
|
* material.text text.css — md-type-*, md-ink-*, and the few classes for text
|
|
* material.visibility hiding an element below or from a breakpoint, over a component's display
|
|
*
|
|
* Every package stylesheet opens with the same layer statement, before its imports, so the order
|
|
* holds whichever file a bundler reaches first. An application's own CSS is unlayered and
|
|
* therefore outranks every package rule, whatever the selector — an application's broad selector
|
|
* (`button { … }`) restyles the components too. foundation/hidden.css keeps its two `!important`
|
|
* rules outside the layers, so `hidden` and `x-cloak` hide an element whatever sets its display.
|
|
*
|
|
* An application still building Tailwind keeps it in a separate entry and opens both entries with
|
|
* `@layer properties, theme, base, material, components, utilities;`, so the `material` layers sit
|
|
* above Tailwind's preflight and below its utilities.
|
|
*/
|
|
|
|
@layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;
|
|
|
|
@import './foundation/reset.css';
|
|
@import './foundation/hidden.css';
|
|
@import './tokens/scheme.css';
|
|
@import './tokens/shape.css';
|
|
@import './tokens/elevation.css';
|
|
@import './tokens/motion.css';
|
|
@import './tokens/type.css';
|
|
@import './tokens/state.css';
|
|
@import './tokens/spacing.css';
|
|
@import './foundation/base.css';
|
|
@import './foundation/interaction.css';
|
|
@import './text.css';
|