- From: Jackie Han <notifications@github.com>
- Date: Tue, 24 Aug 2021 02:02:21 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 24 August 2021 09:02:33 UTC
(I read the spec roughly. This behavior is not defined in the spec.) > This sounds like it might be a chrome bug/behavior? It depends on how to solve the problem. - From the perspective of standard: there should be more explanations or notes for installation related behaviors. - From the perspective of browser implementation: after installation, browser can let the user manually launch the app, like installing a native app. - From the perspective of developers: browser can provide an API for developers to control this behavior. I initially considered from this perspective. On desktop OS, I think chrome's current behavior is inappropriate. But developers have a workaround for it: ``` window.matchMedia('(display-mode: standalone)').addEventListener('change', (evt) => { if(evt.matches) { // display mode changed to 'standalone' after installation location.replace(start_url or other appropriate url); } }); ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/995#issuecomment-904460223
Received on Tuesday, 24 August 2021 09:02:33 UTC