Skip to content

docs: align theme contract with light selector rules and ui.theme reality - #558

Open
Frank-zhu0404 wants to merge 1 commit into
vastsa:mainfrom
Frank-zhu0404:fix/issue-343-theme-docs
Open

Frank-zhu0404 wants to merge 1 commit into
vastsa:mainfrom
Frank-zhu0404:fix/issue-343-theme-docs

Conversation

@Frank-zhu0404

Copy link
Copy Markdown

Summary

  • Document that contributed theme sheets only beat the host when specificity matches, so light-token overrides must use :root[data-theme="light"] (04-plugin-security §3.1 + plugin developer guide).
  • Replace the design-system “MVP: no custom palette” non-goal with built-in system/light/dark plus plugin ui.theme contributions (EN + zh-CN).
  • Fill the theme contract gaps in plugin-development.md: base default dark, assets whitelist/4MB/plugin-asset: rewrite, and windowAppearance (#rrggbb/#rrggbbaa, needs ui.window.appearance), with links to the manifest schema.

Closes #343

Test plan

  • Skim EN/zh diffs for the six doc files
  • Confirm §3.1 specificity note matches tokens.css / hello midnight.css comments
  • Confirm design-system non-goal no longer denies ui.theme

Document that light-token overrides need :root[data-theme="light"],
acknowledge plugin ui.theme contributions in the design-system non-goals,
and fill base/assets/windowAppearance gaps in the plugin developer guide.
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.

主题契约文档与实际行为不一致:特异性规则没写、设计系统仍称「无自定义调色板」

1 participant