Andreas Reinhold / reiniandClaude Opus 5
fb42f004b1
An application lists named schemes in livewire-material.profiles, and material:scheme without a seed generates them all into one stylesheet: the default profile as the plain blocks, every profile under <html data-scheme>, with descendant selectors so a nested data-theme panel keeps the page's profile. The JSON keeps the 1.0 top level. Scheme::resolveProfileUsing() lets the application name the active profile; it is asked on every use and falls back to the default for an unknown name or a resolver that throws. The head script writes it before the first paint and keeps it through wire:navigate, and the mail theme and the error pages' fallback draw it. <x-scheme-picker> chooses one and previews it through $store.theme.previewScheme(); the showcase previews the Workbench's profiles. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy
77 lines
2.6 KiB
JavaScript
77 lines
2.6 KiB
JavaScript
/**
|
|
* The theme, as one piece of state every toggle on the page shares.
|
|
*
|
|
* <x-theme-script> has already decided the theme before this runs; the store starts from
|
|
* what it wrote on <html> (data-theme-choice, data-theme, data-theme-key). `choice` is what
|
|
* the visitor picked — light, dark or system — and `resolved` is what is showing.
|
|
*
|
|
* `value` is an accessor, so binding a control with `x-model="$store.theme.value"` goes
|
|
* through the same write as `set()` and `toggle()`: the attributes, then localStorage.
|
|
*
|
|
* `scheme` is the colour profile on screen (<html data-scheme>, which the server chose), and
|
|
* `previewScheme(name)` shows another one on this page without storing anything — the
|
|
* application saves a choice itself, and the next full load draws what it saved.
|
|
*/
|
|
document.addEventListener('alpine:init', () => {
|
|
const root = document.documentElement
|
|
const media = window.matchMedia('(prefers-color-scheme: dark)')
|
|
const choices = ['light', 'dark', 'system']
|
|
|
|
const resolve = (choice) => (choice === 'system' ? (media.matches ? 'dark' : 'light') : choice)
|
|
|
|
window.Alpine.store('theme', {
|
|
choice: choices.includes(root.dataset.themeChoice) ? root.dataset.themeChoice : 'system',
|
|
resolved: root.dataset.theme === 'dark' ? 'dark' : 'light',
|
|
scheme: root.dataset.scheme || null,
|
|
|
|
get value() {
|
|
return this.choice
|
|
},
|
|
|
|
set value(choice) {
|
|
this.set(choice)
|
|
},
|
|
|
|
set(choice) {
|
|
if (!choices.includes(choice)) {
|
|
return
|
|
}
|
|
|
|
this.choice = choice
|
|
this.resolved = resolve(choice)
|
|
|
|
root.dataset.themeChoice = choice
|
|
root.dataset.theme = this.resolved
|
|
|
|
try {
|
|
localStorage.setItem(root.dataset.themeKey || 'material-theme', choice)
|
|
} catch {
|
|
// Blocked storage: the page still switches, it just will not remember.
|
|
}
|
|
},
|
|
|
|
toggle() {
|
|
this.set(this.resolved === 'dark' ? 'light' : 'dark')
|
|
},
|
|
|
|
previewScheme(name) {
|
|
if (typeof name !== 'string' || !/^[a-z0-9-]+$/.test(name)) {
|
|
return
|
|
}
|
|
|
|
this.scheme = name
|
|
root.dataset.scheme = name
|
|
},
|
|
})
|
|
|
|
// The head script repaints on an OS change while the choice is `system`; this keeps the
|
|
// store's `resolved` — which a toggle's icon reads — in step with it.
|
|
media.addEventListener('change', () => {
|
|
const theme = window.Alpine.store('theme')
|
|
|
|
if (theme.choice === 'system') {
|
|
theme.resolved = resolve('system')
|
|
}
|
|
})
|
|
})
|