desktop-pwas: Define behavior for when a WebApp is previously installed but with a different source |
|
Issue descriptionPendingAppManager 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.
,
Aug 28
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?
,
Aug 29
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 |
|
Comment 1 by ortuno@chromium.org
, Aug 28