Google Git
Sign in
chromium / chromium / src / a600e9a035c98b6da37100102961834570d6cbed
commita600e9a035c98b6da37100102961834570d6cbed[log] [tgz]
authorDevlin Cronin <rdevlin.cronin@chromium.org>Tue Apr 30 17:33:27 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 30 17:33:27 2024
tree29ebd5becef3f7560a034b61ba799c602b6b3f0e
parent88a28b31eeec66c48768d0baca1f65e05be6f5c9 [diff]
[Extensions] Add a manifest v2 experiment manager

Chrome has announced that MV2 extensions will gradually no longer be
supported in the browser. The first step of this is going to be a user-
visible warning, with future stages removing slowly support. 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.

This CL wires up a new ManifestV2ExperimentManager. This class will be
responsible for managing the MV2 experiment state and appropriately
handling affected MV2 extensions. This CL:
* Adds this new manager (as a keyed service)
* Adds a new base::Feature to control the MV2 deprecation warning (this
  feature is disabled)
* Adds a new enum for retrieving the current experiment stage
  (currently, this is just "none" or "warning")
* Adds basic testing for retrieving the experiment stage

It does not introduce any handling or behavior changes affected MV2
extensions.

Bug: 337191307
Change-Id: Ia12c7ee2bb62bb5311e4337afc819a08c13c9737
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5493592
Reviewed-by: Emilia Paz <emiliapaz@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1294447}
9 files changed
tree: 29ebd5becef3f7560a034b61ba799c602b6b3f0e
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. CPPLINT.cfg
  77. DEPS
  78. DIR_METADATA
  79. LICENSE
  80. LICENSE.chromium_os
  81. OWNERS
  82. PRESUBMIT.py
  83. PRESUBMIT_test.py
  84. PRESUBMIT_test_mocks.py
  85. README.md
  86. WATCHLISTS
README.md

Logo Chromium

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.