- From: Daniel Murphy <notifications@github.com>
- Date: Thu, 09 Apr 2026 10:59:10 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 9 April 2026 17:59:15 UTC
dmurph left a comment (w3c/manifest#1092) I propose we split this issue into two: 1) **in-app install detection** Way for a 'browser context with manifest applied' to know if it is installed (e.g. if the web contents is _in_ the app is installed) 2) **in-browser-tab install detection** Way for a 'browser context without manifest applied' but in-scope of installed web app to know if that web app is installed (e.g. site in browser tab that is is-scope of PWA A, can know if PWA A is installed. ) The 2) functionality is solved in Chromium via the getInstalledRelatedApps() API [spec here](https://wicg.github.io/get-installed-related-apps/spec/#dom-navigator-getinstalledrelatedapps). Personally I don't think that `installed: yes` should evaluate in a browser tab, as this is more about the UX. @christianliebel concurs in manifest spec meeting, splitting now. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1092#issuecomment-4216363139 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1092/4216363139@github.com>
Received on Thursday, 9 April 2026 17:59:15 UTC