a36dd2232e
The previous assumption that a proper parent approval must have been granted at the point of enabling the extension is no longer true with the introduction of the SkipParentApprovalToInstall extensions feature, which marks extensions as parent approved in a specific device on Desktop (and approval which should not be synced to other devices). The parent approval is moved at the end of the approval flow callback. Bug: b/336759592 Change-Id: I17c705887a902b3c17c514163617d56ef1df5d5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5497518 Commit-Queue: Finnur Thorarinsson <finnur@chromium.org> Reviewed-by: James Lee <ljjlee@google.com> Auto-Submit: Anthi Orfanou <anthie@google.com> Reviewed-by: Finnur Thorarinsson <finnur@chromium.org> Cr-Commit-Position: refs/heads/main@{#1295371}
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: