Google Git
Sign in
chromium / chromium / src / refs/tags/137.0.7151.103
commit3dcc738117a3439068c9773ccd31f9858923fc4a[log] [tgz]
authorRichard Chen <richche@google.com>Mon Jun 09 18:33:48 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 09 18:33:48 2025
tree75b523f89b8be81b017f87820366743ef4f96211
parent15ce56a8d66b7675279fe7bc8bc9d4b1c2d01404 [diff]
[M137] Add LoadingFromCommandLine histogram

The new Extensions.LoadingFromCommandLine histogram replaces the
previous LoadingFromCommandLineBlocked histogram, which recorded whether
commandline extensions were blocked or not (it should have emitted in
both cases, not just the blocked case). The new histogram will only be
emitted if the commandline loading flags are present and the loading of
commandline extensions is not blocked (due to restrictions or policy).

The histogram records a new enum value LoadExtensionFlag, which
represents either the `--load-extension` or
`--disable-extensions-except` flag.

OBSOLETE_HISTOGRAM[Extensions.LoadingFromCommandLineBlocked]=Replaced by
Extensions.LoadingFromCommandLine

(cherry picked from commit 0d00066f401eea0d90e12ee4331a5d1636b0b028)

Bug: 401529219
Fixed: 422991756
Change-Id: I2c2991898720e87fa07ccf893e4c92114d975673
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6605723
Commit-Queue: Richard Chen <richche@google.com>
Reviewed-by: Anunoy Ghosh <anunoy@chromium.org>
Reviewed-by: Kelvin Jiang <kelvinjiang@chromium.org>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1470340}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6628311
Reviewed-by: Lei Zhang <thestig@chromium.org>
Owners-Override: Srinivas Sista <srinivassista@chromium.org>
Auto-Submit: Richard Chen <richche@google.com>
Commit-Queue: Srinivas Sista <srinivassista@chromium.org>
Cr-Commit-Position: refs/branch-heads/7151@{#1957}
Cr-Branched-From: 8e0d32ed6e49a2415b16e5ed402957cac2349ce2-refs/heads/main@{#1453031}
5 files changed
tree: 75b523f89b8be81b017f87820366743ef4f96211
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. 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.