Re: [w3c/manifest] Add support for defining a theme color for both light & dark modes (prefers color scheme) (#975)

Sascha-Block left a comment (w3c/manifest#975)

It feels like the hard part here isn’t “a second color”, but the constraints around where/when manifests 😅 are consumed:

1) **OS vs browser-engine evaluation**: manifests are used for install/shell integration as well as runtime UI, but CSS media queries are browser-native, not OS-native.

2) **Backwards compatibility**: `theme_color` is a string today; overloading it risks breaking shipped behavior or producing surprising fallbacks.

3) **Selection algorithm**: as soon as we allow more than “default + dark”, we need a normative rule (first/last/specificity) that implementers can align on + interop tests.

4) **Scope creep via icons + localization**: once overrides exist, icons (dark + localized) and i18n negotiation become part of the same design space.

5) **Implementation pressure vs spec clarity**: implementers want to ship, but without a stable shape the ecosystem churns.

Given that, I’d strongly support a minimal v1 (default + dark) with an OS-friendly selection rule, and leave general media-query-style overrides for a future iteration if real demand emerges. ☺️

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/975#issuecomment-3818472422
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/975/3818472422@github.com>