Re: [w3c/manifest] Way to detect if a web app is installed (Issue #1092)

@benfrancis wrote:
> Note that because [deep linking](https://w3c.github.io/manifest/#deep-links) is not widely implemented, it's possible for a URL within the navigation scope of an installed web app with a standalone (or fullscreen or minimal-ui) display mode to be navigated to in an ordinary browsing context (i.e. a browser tab using the default browser display mode) without the manifest being applied. This could result in a situation where the app is "Installed" with a display mode of "standalone", but the current display mode is "browser". It should be made clear what to expect in that common edge case.

Good to think about. We're planning on shipping something like this soon in Chrome (chrome://flags/#enable-user-navigation-capturing-pwa, reimpl option). However - the 'browser' installed mode doesn't have cross-engine consensus here. I think moving forward here with the current proposal, interpreted as 'this is displayed in an installed / standalone window' solves the immediate use-cases here around the display-mode + 'fullscreen' resolution problems. 'installed' might not be the best best name... 'standalone' seems more correct but it's already way too overloaded a term. So 'installed' seems good enough.

This doesn't block us from adding more media queries / values on the Chromium side to expose the 'installed but in the browser' mode in the future. If there is a request for that we can certainly look into it - but I don't think there is (at this point) cross-engine consensus on that yet.

So I'd like to move forward with the proposal of the css media query and the navigator.standalone property.


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

Message ID: <w3c/manifest/issues/1092/2515488152@github.com>