Re: [w3c/manifest] Honor media attribute (#955)

@marcoscaceres I agree that the `media` & `lang` attributes should be honored—as it would indeed solve the problem and it would be a quick win.

But I also agree with @aarongustafson that providing an own manifest per "cartesian product" option (light/dark/high contrast/… * x languages) doesn't scale well. This reminds me of what you need to do in order to specify a pixel-perfect splash screen for iOS Home Screen web apps—not very nice:

```html
<!-- iPhone X (1125px x 2436px) -->
<link rel="apple-touch-startup-image" media="(device-width: 375px) and (device-height: 812px) and (-webkit-device-pixel-ratio: 3)" href="/apple-launch-1125x2436.png">
<!-- iPhone 8, 7, 6s, 6 (750px x 1334px) -->
<link rel="apple-touch-startup-image" media="(device-width: 375px) and (device-height: 667px) and (-webkit-device-pixel-ratio: 2)" href="/apple-launch-750x1334.png">
<!-- iPhone 8 Plus, 7 Plus, 6s Plus, 6 Plus (1242px x 2208px) -->
<link rel="apple-touch-startup-image" media="(device-width: 414px) and (device-height: 736px) and (-webkit-device-pixel-ratio: 3)" href="/apple-launch-1242x2208.png">
<!-- … -->
```
Source: https://appsco.pe/developer/splash-screens


We’re handling things like this in the manifest already by providing a list of icons where the user agent can pick the ones that match based on size, purpose, etc. I feel handling dark/light mode, or high contrast would also fit in there (as an additional property for `ImageResource`s).

@aarongustafson I'm not sure about the `color_schemes` property though, to me it sounds a bit too specific. Looks like a more general approach was discussed in the past: https://github.com/w3c/manifest/issues/186#issuecomment-43824192


Long story short, I agree with @tomayac that we could have both. We should aim for `media`/`lang` support (does this require changes in the spec?) as a part of bringing manifest to CR and discuss adding color scheme awareness for `ImageResource`s and/or the manifest as a whole later or in parallel.

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