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>
112 lines
4.8 KiB
CSS
112 lines
4.8 KiB
CSS
/*
|
||
* <x-carousel-item>: one slide of an <x-carousel>, masked and shifted by the keyline maths
|
||
* carousel.css's header describes, unless the row is full-screen or multi-aspect, where nothing
|
||
* masks it at all (docs/reference/m3/components-actions-communication-containment.md § Carousel).
|
||
*
|
||
* [data-md-carousel-item] the tab stop, a focusable `group`, `md-focus-ring`
|
||
* [data-md-carousel-surface] the masked, shifted, extra-large-corner (28px) box
|
||
* [data-md-carousel-content] the slot (an <img>, cropped)
|
||
* [data-md-carousel-label] the `label` prop's words, over a scrim gradient
|
||
* [data-md-carousel-label-text]
|
||
*
|
||
* The item renders the shared `md-focus-ring` class (foundation/interaction.css) rather than a
|
||
* hand-rolled ring — the box the class draws *is* the item's own whole hit area — refined here to
|
||
* an inset ring, 3px in, its own width (the old `focus-visible:-outline-offset-3`): items sit 8px
|
||
* apart with the row clipping them, so the class's own 2px *outward* offset would be cut off at the
|
||
* row's edges and crowd the next item.
|
||
*
|
||
* Full-screen: edge to edge, no corner, no mask — `--material-carousel-shift`/`-inset` go unread.
|
||
* Multi-aspect: the view writes the item's own `aspect-ratio` inline (`aspect`, a prop, held
|
||
* inside M3's 9:16–16:9 range); the extra-large corner still applies but nothing masks it, since
|
||
* an Arrangement describes items of one size and a multi-aspect row has none. Selectors use `>`
|
||
* throughout, matching carousel.css, so a carousel nested inside an item never inherits its
|
||
* parent's layout rules.
|
||
*
|
||
* The label's ink is a literal `white`, not a role: it sits over `--md-sys-color-scrim`, which is
|
||
* black in every scheme, theme and contrast level, so white is the one ink that always has the
|
||
* scrim's contrast — a role (`inverse-on-surface`) is dark ink in a dark scheme and fails there
|
||
* (deliberately kept).
|
||
*/
|
||
|
||
@layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;
|
||
|
||
@layer material.components {
|
||
[data-md-carousel-item] {
|
||
position: relative;
|
||
height: 100%;
|
||
flex-shrink: 0;
|
||
scroll-snap-align: start;
|
||
scroll-snap-stop: always;
|
||
}
|
||
|
||
[data-md-carousel-item]:focus-visible {
|
||
outline-offset: -3px;
|
||
}
|
||
|
||
[data-md-carousel='full-screen'] > [data-md-carousel-scroller] > [data-md-carousel-item] {
|
||
width: 100%;
|
||
}
|
||
|
||
[data-md-carousel='multi-aspect'] > [data-md-carousel-scroller] > [data-md-carousel-item] {
|
||
width: auto;
|
||
border-radius: var(--md-sys-shape-corner-xl);
|
||
}
|
||
|
||
[data-md-carousel]:not([data-md-carousel='full-screen']):not([data-md-carousel='multi-aspect']) > [data-md-carousel-scroller] > [data-md-carousel-item] {
|
||
width: var(--material-carousel-slot);
|
||
max-width: 100%;
|
||
border-radius: var(--md-sys-shape-corner-xl);
|
||
}
|
||
|
||
[data-md-carousel-item] > [data-md-carousel-surface] {
|
||
position: relative;
|
||
width: 100%;
|
||
height: 100%;
|
||
overflow: hidden;
|
||
background-color: var(--md-sys-color-surface-container-highest);
|
||
color: var(--md-sys-color-on-surface);
|
||
}
|
||
|
||
[data-md-carousel='multi-aspect'] > [data-md-carousel-scroller] > [data-md-carousel-item] > [data-md-carousel-surface] {
|
||
border-radius: var(--md-sys-shape-corner-xl);
|
||
}
|
||
|
||
[data-md-carousel]:not([data-md-carousel='full-screen']):not([data-md-carousel='multi-aspect']) > [data-md-carousel-scroller] > [data-md-carousel-item] > [data-md-carousel-surface] {
|
||
border-radius: var(--md-sys-shape-corner-xl);
|
||
translate: var(--material-carousel-shift) 0;
|
||
clip-path: inset(0 var(--material-carousel-inset, 0px) round var(--md-sys-shape-corner-xl));
|
||
}
|
||
|
||
[data-md-carousel-surface] > [data-md-carousel-content] {
|
||
width: 100%;
|
||
height: 100%;
|
||
|
||
& > img {
|
||
width: 100%;
|
||
height: 100%;
|
||
object-fit: cover;
|
||
}
|
||
}
|
||
|
||
[data-md-carousel-surface] > [data-md-carousel-label] {
|
||
pointer-events: none;
|
||
position: absolute;
|
||
inset-inline: 0;
|
||
bottom: 0;
|
||
display: flex;
|
||
padding: var(--md-sys-measurement-space500) var(--md-sys-measurement-space200) var(--md-sys-measurement-space200);
|
||
background: linear-gradient(to top, color-mix(in srgb, var(--md-sys-color-scrim) 60%, transparent), transparent);
|
||
opacity: var(--material-carousel-label);
|
||
}
|
||
|
||
[data-md-carousel-label] > [data-md-carousel-label-text] {
|
||
overflow: hidden;
|
||
color: white;
|
||
font: var(--md-sys-typescale-title-md);
|
||
letter-spacing: var(--md-sys-typescale-title-md-tracking);
|
||
text-overflow: ellipsis;
|
||
white-space: nowrap;
|
||
translate: var(--material-carousel-label-shift) 0;
|
||
}
|
||
}
|