bc324e05cd
All call sites now go through the SupervisedUserExtensionsDelegate and handle all flow states in one callback method. This change is to prepare for https://chromium-review.googlesource.com/c/chromium/src/+/4163439 and the introduction of a new dialog flow for extension approvals. The existing enums and methods have been renamed to be implementation- agnostic so that they can be used for any UI that invokes the approval flow. One side effect of this change is only allowing one dialog to be open at a time. This was existing behavior for the ManagementAPI and ExtensionEnableFlow, but has been extended to the WebstorePrivateAPI as part of this change. Other than this, no behavior change is expected. Tested: Manually checked the supervised user flows, testing the approve/deny/blocked scenarios. Bug: b:262450453 Change-Id: Id8852249968118ff46ccdafec0fbfb578468997e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4226049 Reviewed-by: Tim <tjudkins@chromium.org> Reviewed-by: Aga Wronska <agawronska@chromium.org> Commit-Queue: Courtney Wong <courtneywong@chromium.org> Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/main@{#1107820}
This will become a reusable extensions module. It implements the core parts of Chrome's extension system, and can be used with any host of the content module.
Some extensions code that is not Chrome-specific still lives in //chrome/browser/extensions and will be moved here.
Technical Documentation: