- From: Ben Francis <notifications@github.com>
- Date: Fri, 30 Jan 2026 03:18:38 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/1092/3823186497@github.com>
benfrancis left a comment (w3c/manifest#1092) > In the editor's meeting we agreed to proceed with an installed CSS media feature and not to proceed with standardization of navigator.standalone. Hi @diekus, are minutes available for this meeting by any chance? I tried to join one of the manifest working sessions recently, but I think the call had ended before I tried to join, and then I realised perhaps they are only open to editors. I would be interested to understand the rationale behind this decision, and under what circumstances the "installed" media query would evaluate to yes. @marcoscaceres It sounds from your comment above that from a Safari browser tab "installed" would evaluate to "no" even if the current document falls within the scope of a web app which is installed on the OS, for privacy reasons. I can understand the rationale behind that, but it does seem to make the feature useless for deciding whether to display an install button for example. What are the use cases it _is_ useful for, and if "installed" is only "yes" if the document is currently displayed in an application context with a non-browser display mode, then how will the `installed` media query differ from the existing `display-mode` media query which largely already serves that purpose? Thanks -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1092#issuecomment-3823186497 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1092/3823186497@github.com>
Received on Friday, 30 January 2026 11:18:42 UTC