Skip to content

fix: stop forcing color-scheme light so native controls follow the OS - #351

Merged
MaximeGaudin merged 1 commit into
mainfrom
fix/issue-141-color-scheme
Aug 29, 2026
Merged

fix: stop forcing color-scheme light so native controls follow the OS#351
MaximeGaudin merged 1 commit into
mainfrom
fix/issue-141-color-scheme

Conversation

@MaximeGaudin

Copy link
Copy Markdown
Owner

Summary

  • styles.css set color-scheme: light on :root with a single hardcoded light palette and no prefers-color-scheme handling, so the site forced light-themed native controls (scrollbars, form widgets) even for visitors in dark mode.
  • The docs design is a deliberately crafted light-only "cool mist + ink console" palette (978 lines of light-theme CSS), so this takes the issue's first resolution: commit to light-only and drop the color-scheme: light forcing. With no color-scheme set, the page palette stays exactly as designed while native widget theming follows the visitor's OS preference.
  • A short comment records the intentional omission so it is not "fixed" back later.

Fixes #141

Test plan

  • pnpm run build in apps/docs: 48 pages built successfully.
  • pnpm run lint (biome + astro check + check-no-todos): 0 errors, 0 warnings, clean.
  • CI green on the PR

@MaximeGaudin
MaximeGaudin merged commit 7be3bdd into main Aug 29, 2026
8 checks passed
@MaximeGaudin
MaximeGaudin deleted the fix/issue-141-color-scheme branch August 29, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs site: no dark mode support — color-scheme is hardcoded to light with no prefers-color-scheme handling

1 participant