
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}
Chrome
This directory contains the open source, application layer of Google Chrome.
Unlike other parts of Chromium like //content, which provide framework intended to support multiple products, this directory contains code that is focused on building specific products with opinionated UX.
Specific products include:
- Chrome desktop browser for Chrome OS, Windows, Mac and Linux
- Chrome mobile browser for Android
- Chrome OS system UI
See //ios/chrome for the Chrome mobile browser for iOS, and note that code that is shared between //chrome and //ios/chrome is typically factored out into //components.