Skip to content

docs: one section for theme name bindings, and no dark in the examples - #6000

Open
manolo wants to merge 3 commits into
mainfrom
docs/theme-name-binding-sections
Open

docs: one section for theme name bindings, and no dark in the examples#6000
manolo wants to merge 3 commits into
mainfrom
docs/theme-name-binding-sections

Conversation

@manolo

@manolo manolo commented Sep 10, 2026

Copy link
Copy Markdown
Member

Fixes #5995

  • One section for theme name bindings instead of two.
  • No dark in the examples: theme names are variants like small.
  • Theming page: @ColorScheme and Page.setColorScheme() are the color scheme API, the dark theme name is a Lumo selector on <body>, and tests assert getColorScheme().

Two sections on the same page taught the same thing, and both used "dark"
as the example theme name, which reads as the way to switch an application
to dark mode. It is not: the theme attribute lands on the component, and
under Aura it does nothing at all.
@manolo
manolo requested a review from jouni September 10, 2026 13:09
@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown

Preview Deployment

This PR has been deployed for preview.

URL: https://docs-preview-pr-6000.fly.dev

Changed pages

Added content is highlighted in green; removed content is marked in red on each page.

Built from 9520718

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.

Hackathon 25.3: say that Page.setColorScheme is the dark mode API, and that theme="dark" is a Lumo selector rather than a second one

1 participant