- From: Aaron Gustafson <notifications@github.com>
- Date: Wed, 24 Feb 2021 10:27:12 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/955/785280619@github.com>
We are working to [make `ImageResource` color scheme aware](https://github.com/w3c/image-resource/issues/26), which would solve part of this challenge. I think one of the challenges with having multiple manifests is that you then have to maintain those separate manifests, which makes it more likely they will get out of sync. Your use case is light/dark mode, but there are all high contrast media queries and the potential for exponential manifests as different media queries for screen size, etc. get applied (e.g., a different manifest for small screens vs. large ones). Setting aside the potential maintenance headache for the developer when it comes to maintenance, there’s also the complexity this creates for implementors (having to track which manifest should apply in which scenario) and there’s also the possibility users could get wildly different app experiences based on which manifest is loaded (e.g., different manifests get applied based on whether DevTools is open or not). I think the use case outlined (color modes) is worth addressing (which is why [I am pursuing it for `ImageResource`](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ImageResource-color_scheme/explainer.md)) but I am not sure adding media query-aware manifest loading is the answer. Would love to hear thoughts from @marcoscaceres @kenchris @mgiuca and @christianliebel on this as well. -- 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-785280619
Received on Wednesday, 24 February 2021 18:27:24 UTC