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>
95 lines
3.9 KiB
CSS
95 lines
3.9 KiB
CSS
/*
|
|
* The colour-role table M3's semantic colours share, so a component that offers the same set of
|
|
* roles does not repeat it: `data-md-color` picks primary (most components' default, drawn
|
|
* without the attribute), secondary, tertiary, error, success, warning or info, and this sets the
|
|
* four generic variables a component's own stylesheet reads — `--md-color`/`--md-on-color` the
|
|
* role itself, `--md-container`/`--md-on-container` its tonal container.
|
|
*
|
|
* A component gives its own prefixed variables (`--md-badge-color`, …) a fallback of its default
|
|
* role, `var(--md-color, var(--md-sys-color-<default>))`, so the generic ones only take over once
|
|
* `data-md-color` is actually written on that element. The four are registered as not inheriting,
|
|
* so a component inside a coloured one (a badge on an error button) still falls back to its own
|
|
* default rather than taking its ancestor's role. A component whose primary
|
|
* deliberately reads secondary-container instead of primary-container (button.css, slider.css,
|
|
* progress.css) keeps a small override of its own for an explicit `data-md-color="primary"` too:
|
|
* this file's `primary` entry is the plain M3 mapping every other role, and every other component,
|
|
* wants.
|
|
*
|
|
* A component that supports only part of this set (fab.css's primary/secondary/tertiary) does not
|
|
* import this file: wiring it in would make every role it leaves out suddenly take effect through
|
|
* the bare `[data-md-color]` selector below, a behaviour change rather than a rewrite.
|
|
*/
|
|
|
|
@layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;
|
|
|
|
@layer material.components {
|
|
@property --md-color {
|
|
syntax: '*';
|
|
inherits: false;
|
|
}
|
|
|
|
@property --md-on-color {
|
|
syntax: '*';
|
|
inherits: false;
|
|
}
|
|
|
|
@property --md-container {
|
|
syntax: '*';
|
|
inherits: false;
|
|
}
|
|
|
|
@property --md-on-container {
|
|
syntax: '*';
|
|
inherits: false;
|
|
}
|
|
|
|
[data-md-color='primary'] {
|
|
--md-color: var(--md-sys-color-primary);
|
|
--md-on-color: var(--md-sys-color-on-primary);
|
|
--md-container: var(--md-sys-color-primary-container);
|
|
--md-on-container: var(--md-sys-color-on-primary-container);
|
|
}
|
|
|
|
[data-md-color='secondary'] {
|
|
--md-color: var(--md-sys-color-secondary);
|
|
--md-on-color: var(--md-sys-color-on-secondary);
|
|
--md-container: var(--md-sys-color-secondary-container);
|
|
--md-on-container: var(--md-sys-color-on-secondary-container);
|
|
}
|
|
|
|
[data-md-color='tertiary'] {
|
|
--md-color: var(--md-sys-color-tertiary);
|
|
--md-on-color: var(--md-sys-color-on-tertiary);
|
|
--md-container: var(--md-sys-color-tertiary-container);
|
|
--md-on-container: var(--md-sys-color-on-tertiary-container);
|
|
}
|
|
|
|
[data-md-color='error'] {
|
|
--md-color: var(--md-sys-color-error);
|
|
--md-on-color: var(--md-sys-color-on-error);
|
|
--md-container: var(--md-sys-color-error-container);
|
|
--md-on-container: var(--md-sys-color-on-error-container);
|
|
}
|
|
|
|
[data-md-color='success'] {
|
|
--md-color: var(--md-sys-color-success);
|
|
--md-on-color: var(--md-sys-color-on-success);
|
|
--md-container: var(--md-sys-color-success-container);
|
|
--md-on-container: var(--md-sys-color-on-success-container);
|
|
}
|
|
|
|
[data-md-color='warning'] {
|
|
--md-color: var(--md-sys-color-warning);
|
|
--md-on-color: var(--md-sys-color-on-warning);
|
|
--md-container: var(--md-sys-color-warning-container);
|
|
--md-on-container: var(--md-sys-color-on-warning-container);
|
|
}
|
|
|
|
[data-md-color='info'] {
|
|
--md-color: var(--md-sys-color-info);
|
|
--md-on-color: var(--md-sys-color-on-info);
|
|
--md-container: var(--md-sys-color-info-container);
|
|
--md-on-container: var(--md-sys-color-on-info-container);
|
|
}
|
|
}
|