A PWA with a fullscreen manifest display mode is displayed as standalone (windowed) in Windows
Reported by
le...@devliber.com,
Jun 7 2018
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.79 Safari/537.36 Steps to reproduce the problem: 1. Create a Progressive Web App (PWA) with a fullscreen display mode in the web app manifest 2. Open it in Windows 10 and Chrome, and install the PWA 3. Open the PWA from its desktop shortcut Test project: https://pwadtest.hwalab.com/fullscreen/ https://github.com/hwalab-developer/PWADisplayTest What is the expected behavior? The fullscreen PWA should open with a fullscreen display mode, "without any browser UI and taking up the entirety of the available display area". What went wrong? The fullscreen PWA opens in a window, with a standalone display mode, not with a fullscreen display mode as expected. The display-mode CSS media feature also reports that the application's display mode is standalone, not fullscreen as expected. Did this work before? No Does this work in other browsers? N/A Chrome version: 67.0.3396.79 Channel: stable OS Version: 10.0 Flash Version: The minimal-ui display mode also does not work, and it is displayed as standalone.
,
Jun 8 2018
,
Jun 14 2018
Tested the issue on chrome reported version 67.0.3396.79 using Windows-10 with steps mentioned below: 1) Launched chrome reported version and navigated to URL: https://pwadtest.hwalab.com/fullscreen/ 2) Observed Manifest display mode: fullscreen & Actual display mode: browser @Reporter: Please find the attached screenshot for your reference and provide your feedback on it. Thanks!
,
Jun 15 2018
@viswa.karala@chromium.org If you launch it in browser, of course the Actual display mode will be browser. You have to install the Progressive Web App (PWA) first, by clicking the Install App link in the footer of the page, or by using the "Install fullscreen PWA Display Test..." menu item in Chrome. Then you have to click Install in the web app install prompt. Then launch PWA Display Test from the Windows shortcut, and you will observe Manifest display mode: fullscreen & Actual display mode: standalone Please see attached screenshots.
,
Jun 15 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 5
Tried to reproduce the issue by following below steps. 1.Downloaded the zip file from link -https://github.com/hwalab-developer/PWADisplayTest 2. Tried adding the extension from chrome://extensions and could see the error "Manifest file is missing or unreadable". Attached is the screen cast for reference. @reporter : Request you to check and confirm if anything is missed from our end in reproducing the issue and any further information will help in better triaging.. Thanks !
,
Jul 11
It's not a Chrome extension, it's a Progressive Web App (PWA) https://en.wikipedia.org/wiki/Progressive_Web_Apps https://developers.google.com/web/progressive-web-apps/ https://developers.google.com/web/updates/2018/05/dpwa https://www.xda-developers.com/progressive-web-apps-chrome-how-to/ etc. Attached are the enabled "chrome://flags/" on my installation.
,
Jul 11
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 5
,
Nov 5
We have not yet implemented the fullscreen display mode for desktop. As per the web app manifest spec, this is substituted with standalone windowed mode.
,
Nov 5
To clarify, we are fully spec compliant in *not* supporting the fullscreen display mode: https://www.w3.org/TR/appmanifest/#dfn-fallback-display-mode "Each display mode, except browser, has a fallback display mode, which is the display mode that the user agent can try to use if it doesn't support a particular display mode. ... The fallback display mode for fullscreen is standalone." Having said that, we'd like to implement fullscreen but it isn't a priority (there are security issues we'd have to figure out, since we wouldn't be showing the origin when the user opens the app). |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by le...@devliber.com
, Jun 7 20186.8 KB
6.8 KB View Download
15.4 KB
15.4 KB View Download