Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

audit: Can prompt recurring visitor to install to homescreen

See original GitHub issue

Manual evaluation: manifest has short_name, 144x144 png icon

input:

parsed manifest - #22

audit:

has a registered SW
valid start_url
valid name
valid short_name
icon of size >= 144x144 and png (either type image/png or filename ending in .png)

update: ^ Copied from brendan’s comment below.

See also “PWA validator” bookmarklet - #17

docs: install-to-homescreen on /web

when:

page loaded and in idle state

Issue Analytics

State:
Created 8 years ago
Comments:12 (12 by maintainers)

Top GitHub Comments

1reaction

brendankennycommented, Jan 4, 2017

manifest has a valid name and valid shortname

this one has been confusing because of the difference in context of use of the short_name. See #348, for instance. We should add a clear comment on this when we fix this 😃

It doesn’t look at standalone/fullscreen

IMO we should get rid of the manifest display audit and rename it chrome-a2hs-display.js or whatever to make it clear what it is and test only for standalone/fullscreen

0reactions

paulirishcommented, Jul 13, 2018

Looked again at the current implementation (installable_manager.cc and app_banner_manager.cc):

is secure
- is either localhost or has a valid SSL Certificate
has a service worker
- it must control the current url and the manifest’s start_url
valid_manifest
- has a valid starturl
- has either a name or shortname (that isn’t an empty string)
- display is standalone/fullscreen/minimal-ui
has a satisfactory icon
- must be a png
- must be square
- must be at least 72px, but chrome much prefers 144px or larger.
has sufficient engagement
- currently requires a 2. see at chrome://site-engagement/