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

carlosjeurissen left a comment (w3c/manifest#975)

@dmurph [mentioned](https://github.com/w3c/manifest/issues/975#issuecomment-3861957403):
> For 'constraints not known'.... I 'think' that is OK? I guess for supporting backwards compatibility, if a new constraint is added... yeah you would need to have entries without that new constraint anyways.... so that seems fine....

What does OK mean in this sense? Do you agree the icon group should be ignored in the initial search? (Unless the final result is null/0). Indeed for backwards compatibility, you would have to add entries without this constraint/property. However we should specify what should happen when unknown/unsupported properties/values are encountered.

> if there is a problem with this precidence (e.g. the dark-maskable-french example above where it used the non-french icon due to no french icon specified that was dark), the developer can simply just add the french-maskable-dark icon and fix it.

In that case we are back to the duplication problem. Which the precedence author-defined order would solve.

One more note on dark icons: for webExtensions, icons are mostly transparent. Dark icons are also used in light mode when a browser theme is used with a dark background (like olive green for example). It uses it as clue as what background works well. However seems with the introduction of the liquid glass dark app icons. "dark mode icons" means more than icons working well on a dark background.

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

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