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>
28 lines
1.7 KiB
PHP
28 lines
1.7 KiB
PHP
{{-- The AM/PM radio group, drawn once here and included from both the dial and the typing mode of
|
|
resources/views/components/timepicker.blade.php, since the two draw it byte for byte alike. --}}
|
|
<div
|
|
data-md-timepicker-period
|
|
role="radiogroup"
|
|
aria-label="{{ __('Select AM or PM') }}"
|
|
x-show="! is24"
|
|
x-on:keydown.arrow-right.prevent="movePeriod($event)"
|
|
x-on:keydown.arrow-left.prevent="movePeriod($event)"
|
|
x-on:keydown.arrow-down.prevent="movePeriod($event)"
|
|
x-on:keydown.arrow-up.prevent="movePeriod($event)"
|
|
>
|
|
@foreach ([false => 'am', true => 'pm'] as $pm => $period)
|
|
<button
|
|
type="button"
|
|
data-md-timepicker-period-option="{{ $period }}"
|
|
class="md-state-layer md-focus-ring"
|
|
role="radio"
|
|
aria-checked="false"
|
|
x-bind:aria-checked="({{ $pm ? '' : '! ' }}isPm).toString()"
|
|
x-bind:tabindex="({{ $pm ? '' : '! ' }}isPm) ? 0 : -1"
|
|
x-bind:disabled="! periodAllowed({{ $pm ? 'true' : 'false' }})"
|
|
x-on:click="setPeriod({{ $pm ? 'true' : 'false' }})"
|
|
x-text="periods[{{ (int) $pm }}]"
|
|
>{{ $pm ? __('PM') : __('AM') }}</button>
|
|
@endforeach
|
|
</div>
|