Load the early theme script from a file so the CSP allows it
Production's Content-Security-Policy has no script-src, so it falls back to default-src 'self' and blocks inline scripts. The inline head script that applied the saved theme never ran on prod, leaving the page on the system theme while the selector showed the saved choice. Move it to resources/js/theme-init.js, built by esbuild alongside app.js into a minified, source-mapped file loaded as a blocking script in the head. ThemeSelector now also applies the saved colour scheme, so the page and buttons can't disagree. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
5483712e29
commit
7dbf4a3311
1 changed files with 31 additions and 13 deletions
|
|
@ -5,6 +5,10 @@ class ThemeSelector {
|
|||
this.btnDark = this.widget.querySelector('#btn-dark');
|
||||
this.status = this.widget.querySelector('#theme-status');
|
||||
this.currentTheme = ThemeSelector.storedTheme();
|
||||
if (this.currentTheme !== 'system') {
|
||||
/* backstop in case theme-init.js didn't run, so the page always matches the buttons */
|
||||
document.documentElement.style.setProperty('color-scheme', this.currentTheme);
|
||||
}
|
||||
this.updateButtons();
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue