- From: Alexander Kyereboah <notifications@github.com>
- Date: Wed, 10 Jun 2026 13:40:47 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 10 June 2026 20:40:51 UTC
kyerebo left a comment (w3c/manifest#1218) > @kyerebo we generally do it here because we understand the context/usage better than the CSS WG - plus a lot of us who work on this are not members of the CSS WG. > > However, once it stabilizes, we can certainly upstream it to the CSS WG for maintenance. > > At the same time, we would get the CSS WG members to review this before merging it. Thanks for the clarification, that makes sense to me. It'd be great to have a CSS WG member review this to avoid future friction when trying to upstream it. > @marcoscaceres wrote: > > > @benfrancis wrote: > > > Maybe application-context should just have a boolean value? > > > Yeah, I’m kinda landing in the same place. > > Am I missing something or does the version being reviewed still have two string values rather than a boolean? I'm also still seeing the enumerated media feature, could we have the spec text reflect the boolean media feature version (e.g. `@media (application-context)` or `@media not (application-context)`)? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/pull/1218#issuecomment-4674267321 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/pull/1218/c4674267321@github.com>
Received on Wednesday, 10 June 2026 20:40:51 UTC