- From: Darien Maillet Valentine <notifications@github.com>
- Date: Sun, 07 Aug 2022 08:14:07 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 7 August 2022 15:14:19 UTC
> But I think what you're saying is that there's precedent for having a subset of MQ selectors without using the CSS MQ syntax. Yep! Though I suspect it could also lead to a nice kinda symmetry story if implementing fallback/robustness behaviors alongside the overrides. One might choose to leverage the sec-ch-* & vary headers to determine _non-override_ values in a manifest response alongside the new overrides. If the agent doesn’t yet understand manifest overrides but does implement sec-ch-* (like current Chromium), you’d get likely sensible initial behavior even though it wouldn’t automatically respond to things like a dynamic change to system color scheme. I wouldn’t expect most folks to bother going that far I guess, but if the common pattern could make it a little more attractive/intuitive as a progressive enhancement strategy in some use cases. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1045#issuecomment-1207428967 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1045/1207428967@github.com>
Received on Sunday, 7 August 2022 15:14:19 UTC