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

marcoscaceres left a comment (w3c/manifest#975)

@aarongustafson, 
> do we want to make the system flexible to allow for other color adjustments like forced-colors, inverted-colors or monochrome while we're devising it?

We checked and a lot of those are computed and didn't apply in case of installation from a manifest (or could be handled in CSS itself once the app starts). Thus, we didn't see "forced-colors, inverted-colors or monochrome" becoming "a thing" that we would need to worry about in this spec with the properties that we have.  

@dmurph: 
> I would love to not pollute the root namespace of the object if that is the direction we go. e.g. we choose a name for the dictionary to be under

Not sure I follow? `"overrides"` is not a thing, is it? If the object just contains other objects, then theoretically it can just be collapsed away (hence `"color_scheme_dark"` at the top-level). I guess my point being, `"overrides"` "pollutes" equally as just having `"color_scheme_dark"`. 
 

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

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