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

Issue 896575 link

Starred by 2 users
Status: Assigned
Owner:
dominickn@chromium.org
Cc:
█ mgiuca@chromium.org
█ ortuno@chromium.org
benwells@chromium.org
dominickn@chromium.org
█ bgalbs@google.com
pcovell@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Desktop PWAs] Allow default app and system app install from just a Manifest URL

Project Member Reported by calamity@chromium.org, Oct 18 
Default and System Apps shouldn't have to do a heavy page load in order to point to a manifest for install.

System Apps currently have an ultralight pwa.html that simply has a link rel=manifest tag. They should be able to just install by specifying the manifest URL in the SystemWebAppManager instead.

Comment 1 by mgiuca@chromium.org, Oct 19

Cc: ortuno@chromium.org benwells@chromium.org
Very similar ask to what we've been talking about with policy (being able to install via a manifest URL, rather than having to create a lightweight HTML page to link to the manifest URL). I didn't think of the fact that the background page actually has to load a (potentially heavy) page in the background.

Comment 2 by mgiuca@chromium.org, Jan 4

Cc: mgiuca@chromium.org
Owner: dominickn@chromium.org
Assigning to Dominick (long-term architecture issue).

Comment 3 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment