1893232 - Consider including origins in update prompt for mv3 extensions

Status: NEW

(WebExtensions :: General, enhancement, P3)

Description

[Tomislav Jovanovic :zombie]

Bug 1889402 is introducing origin permissions into install flow for mv3 extensions, but not during updates.

It is not clear that including them would be the the best choice in all situation:

• Updates are already a pain point, being blocked on user accepting them if there are new permissions,
• But we already don't consider origin permissions as blocking for mv3 installs, we plan to continue (in certain cases) installing extensions without granting them all requested origin permissions.
• So presenting an ultimatum of "grant these new origin permissions to update the extension" to the user is appropriate.
• And I'm really not sure we want to complicate the update flow to include UI for granting/not origin permissions.

So filing this as a followup.

Comment 1

[Paul Rouget (ex-mozilla)]

I was wondering if there were any update on this?

We are planning a big update on Video DownloadHelper (migrating to V3), but apparently, the host permission changes will force our user to manually accept all the new permission.

Comment 2

[Rob Wu [:robwu]]

(In reply to Paul Rouget (ex-mozilla) from comment #1)

I was wondering if there were any update on this?

We are planning a big update on Video DownloadHelper (migrating to V3), but apparently, the host permission changes will force our user to manually accept all the new permission.

What behavior would you like to have, concretely?

Currently the behavior for MV2 is to not update until the user has approved the increased permissions,
and in MV3 the extension is updated without adding the requested host permission (it still pauses updates for regular API permissions).

In the WECG there is a proposal that allows extension authors to explicitly specify the desired behavior for all permissions on update: https://github.com/w3c/webextensions/pull/798