Re: [w3c/manifest] Add `application-context` CSS media feature (PR #1218)

benfrancis left a comment (w3c/manifest#1218)

@dmurph wrote:
> I was told at some point that enum media queries are preferred over booleans, for future proofing, but idk where I was told that I could be misremembering. We can also define the boolean evaluation of this media query, I believe, while keeping it an enum

I see. I think the challenge is just what strings to use that don't just add to the confusion!

I think `display-context: application` and `display-context: browser` would make sense _if_ the browser display mode was deprecated in app manifests. (I was originally going to suggest `browsing-context: application` and `browsing-context: browser`, but given the proposed changes in terminology to refer to "top-level traversable" instead of "browsing context" I'm not sure if that might be confusing.)

Otherwise, looking at other existing media queries I see "none" is often used as an off state so:

`application-context: none` and `application-context: application` could work?

I agree with @kyerebo that it might be a good idea to get input from the CSS WG so it's something they're happy with from a consistency and extensibility point of view etc.

> this was in reference to the privacy/security considerations

Ah OK I understand. Yes it doesn't expose much more information than was already available from a privacy point of view, since `standalone` and `minimal-ui` display modes are currently only possible inside an application context so the application context is detectable most of the time.

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

Message ID: <w3c/manifest/pull/1218/c4680032251@github.com>