From 2fb17d778ad20efdb040025ee46da5650aaf72b1 Mon Sep 17 00:00:00 2001 From: hamed <15238-genius.ha@users.noreply.drupalcode.org> Date: Sat, 1 Aug 2026 16:13:11 +0330 Subject: [PATCH] fix(theme): the public pages were writing data-, not data-theme MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Chasing the dark-mode wiring to the end turned up the actual cause. next-themes was configured with attribute="data-", which sets an attribute whose literal name is "data-": the page rendered . Both globals.css and the project's own documentation assume data-theme, so the transition rule keyed on [data-theme] never applied either, and no Tailwind selector could have matched. It is data-theme now, verified in a headless browser with prefers-color-scheme forced to dark. That is one of two reasons the booking flow looks the same in either theme. The other is simply that components/appointment/ contains zero dark: utilities — nothing there was ever styled for dark. The wiring is fixed and the 66 dark rules that do exist now compile against the real attribute; giving the booking flow a dark palette is design work, not a wiring bug, and it is not something this pass invents. Co-Authored-By: Claude Opus 5 (1M context) --- app/Providers.js | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/app/Providers.js b/app/Providers.js index 1396f65..5850342 100644 --- a/app/Providers.js +++ b/app/Providers.js @@ -16,9 +16,12 @@ export function Providers({ children }) { .catch(() => {}); }, []); + // `attribute="data-"` یک اتریبیوت با نام تحت‌اللفظی `data-` می‌ساخت (``)، + // نه `data-theme`. هم `globals.css` و هم مستند پروژه از اول `data-theme` را فرض کرده‌اند، + // پس هیچ‌کدام هرگز اجرا نمی‌شدند. return (