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

Issue 878262 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

desktop-pwas: Define behavior for when a WebApp is previously installed but with a different source

Project Member Reported by ortuno@chromium.org, Aug 28

Issue description

PendingAppManager is used by WebAppPolicyManager, Default Apps, and Android Messages. It's possible that a policy includes a Default Installed app or vice versa. We should define what should be the outcome in this case. The options are:

1. Fail the second install, regardless of whether it is from policy or default app.
2. Re-install the app based on the second install source.
3. Re-install only if the second install is from policy.
 
nigeltao mentioned an open question and implementation details:

What should the return value be for Install/InstallApps? Should it be an empty string or the id of the already installed app.

This probably involves (1) passing a Manifest::Location to [MaybeStartNextInstallation], and (2) in IsExtensionPresentAndInstalled, comparing it to extension->location().
Possibly we should just return a struct through the InstallCallback that indicates a status with an enum:

kInstallSuccess
kAlreadyInstalled
kInstallFailure

The removal aspect is a fairly interesting discussion. My initial thought is that policy should subsume default apps, since an app being removed from policy should just not be installed full stop. On that note... maybe there should be a policy to not install default apps at all?
I agree with your initial thought.

I don't think we should make it a policy to not install default apps. Some of our default apps might also be things admins force install, for example Google Docs.

Sign in to add a comment