New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 690987 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

superbowl.com passes Lighthouse A2HS checks but isn't installed as a WebAPK

Project Member Reported by sbirch@chromium.org, Feb 10 2017

Issue description

I can repro this on Canary.
 
Owner: zpeng@chromium.org
Status: Assigned (was: Available)
Felix, can you please take a look?

Comment 2 by zpeng@chromium.org, Mar 2 2017

Cc: pkotw...@chromium.org
Status: WontFix (was: Assigned)
Lighthouse accepts a lot more "display" modes defined in W3C Web Manifest:
Chrome only accepts Standalone & Fullscreen,
see https://cs.chromium.org/chromium/src/chrome/browser/installable/installable_manager.cc?rcl=20032a5cd3037ac303100cae6585e279d6908c23&l=380

while Lighthouse accepts 'browser', 'fullscreen', 'minimal-ui', 'standalone'
see 
https://github.com/GoogleChrome/lighthouse/blob/9f91ab405ca89882f40a71c6aef5dc6dc08543b4/lighthouse-core/audits/manifest-display.js#L43

In the case of superbowl.com, the display field is left unset. Lighthouse assigns "browser" by default and accepts it, while Chrome rejects the Web Manifest.

(Lighthouse assigns "browser" by default, see
https://github.com/GoogleChrome/lighthouse/blob/9f91ab405ca89882f40a71c6aef5dc6dc08543b4/lighthouse-core/test/audits/manifest-display-test.js#L54)



Sign in to add a comment