commit | 0bf793fc36ff7cd805c4f9134224a135a7deeea8 | [log] [tgz] |
---|---|---|
author | EmiliaPaz <emiliapaz@chromium.org> | Tue Jul 09 04:53:25 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 09 04:53:25 2024 |
tree | 246da5b6d29ad6c41229edd4506b797a0e7f6838 | |
parent | 6cb09a503810977f2394f060211028667d7b76ff [diff] |
[Extensions] Handle extension acknowledgment of MV2 disabled stage Chrome has announced that MV2 extensions will gradually no longer be supported in the browser. None of these changes will take effect on any Chrome channel before June, 2024. See more information at https://developer.chrome.com/blog/resuming-the-transition-to-mv3. The second stage of the deprecation will disable unsupported MV2 extensions and has user-visible notices in chrome://extensions. This CL connects the 'keep for now' button in the extension's action menu to acknowledge the notice for the rest of the stage. This means when the button is clicked: - extension is removed from mv2 deprecation panel in chrome://extensions - mv2 deprecation message in chrome://extensions detail page is hidden for the rest of the stage. For this we: - Notify ManifestV2ExperimentManager to update the "extension acknowledged in disabled stage" via developerPrivate.updateExtensionConfiguration - Listen for "extension acknowledged in disabled stage" pref changes via extension info updates Screencast: https://drive.google.com/file/d/1aE0DL8oDD7rDYTdMsjuFFC5FWwWh4PMc/view?usp=drive_link First, we open a browser in exp stage 1 (warning) and dismiss the notice. Then, we open a browser in exp stage 2 (disabled), which has the notice again, and dismiss the notice. Bug: 339061151 Change-Id: I3ac8a5e7372a650d8972d39ae68f68cfc0df233f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5666466 Auto-Submit: Emilia Paz <emiliapaz@chromium.org> Reviewed-by: Rebekah Potter <rbpotter@chromium.org> Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/main@{#1324668}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.