{{-- The theme and the navigation rail's width, decided before the first paint. Include it in , ahead of @vite. It reads the visitor's choice from localStorage (`livewire-material.theme.storage_key`): `light`, `dark` or `system`, falling back to `theme.default`. `system` follows the operating system, now and whenever it changes. The result is written to , which is the only thing the stylesheet keys on; the choice itself is , where `$store.theme` picks it up. A value under one of `theme.legacy_keys` — an earlier toggle's key, which may be JSON-encoded (maryUI's `"dark"`) — is adopted once and removed. Nothing is written for a visitor who never chose, so changing `theme.default` later reaches them too. With colour profiles (`livewire-material.profiles`, generated by `material:scheme`), the active one — `Scheme::profile()`, which asks the application's resolver — is written to , which the generated stylesheet keys each profile on. The rail rides along for the theme's reason: is `expanded` or `collapsed` (`livewire-material.rail.storage_key`, falling back to `rail.default`), and a collapsible rail's width is CSS keyed on it (the `rail-collapsed:` variant). Set any later, a collapsed rail would paint wide and snap shut on every load. `$store.rail` (resources/js/navigation.js) changes it. rides with it and says nothing was stored — the value is only `rail.default`, not a choice — so ``'s adaptive rail can start collapsed in the expanded class (840–1199) and expanded from large, as M3 asks, while still obeying a visitor who has chosen. `$store.rail` drops it the first time they do. With `theme.meta` on, the browser's own chrome follows too: the `content` of every without a `media` attribute — one is added to when there is none — is the resolved theme's `surface`, from the scheme file (`Scheme`), for the profile in (else the active one). A MutationObserver on keeps it in step with whatever changes `data-theme` or `data-scheme` afterwards: `$store.theme.set()` and `toggle()`, an OS change while `system`, a profile preview, the application's own script. A layout's own theme-color meta belongs before this script: one written after it is only painted on DOMContentLoaded, beside the one added here. Off by default, and then none of it is emitted. wire:navigate swaps the body, merges the head without running this again, and gives the next page's attributes — which the server rendered without any of these, so Livewire removes them. They are put back as the new page is swapped in (`onSwap`, in the same task, before anything paints), so this only has to run on a full load. The head merge also puts the next page's server-rendered theme-color meta in place of the painted one, so it is painted again there, and once more on `livewire:navigated`. --}} @php $theme = config('livewire-material.theme'); $rail = config('livewire-material.rail'); $settings = [ 'scheme' => \NoNameWeb\LivewireMaterial\Support\Scheme::profile(), 'default' => in_array($theme['default'] ?? null, ['light', 'dark', 'system'], true) ? $theme['default'] : 'system', 'key' => $theme['storage_key'] ?? 'material-theme', 'legacy' => array_values($theme['legacy_keys'] ?? []), 'rail' => [ 'default' => ($rail['default'] ?? null) === 'collapsed' ? 'collapsed' : 'expanded', 'key' => $rail['storage_key'] ?? 'material-rail', ], ]; // Only the surfaces the meta can show: the active scheme's, and every profile's for a preview. if ((bool) ($theme['meta'] ?? false)) { $surfaces = fn (array $scheme): array => ['light' => $scheme['light']['surface'], 'dark' => $scheme['dark']['surface']]; $schemeProfiles = \NoNameWeb\LivewireMaterial\Support\Scheme::profiles(); $settings['meta'] = [ // PHP 8.5 deprecates a null array offset: without profiles the scheme is null. ...$surfaces(($settings['scheme'] !== null ? ($schemeProfiles[$settings['scheme']] ?? null) : null) ?? \NoNameWeb\LivewireMaterial\Support\Scheme::load()), 'profiles' => (object) collect($schemeProfiles)->map($surfaces)->all(), ]; } @endphp