Reland "Implement a simple mechanism for downstream forks to customize runtime-enabled-features.json5"

Ensure file_paths are only updated if there are items that are added/changed.

Original Description:

This is a change to the runtime-enabled-featured build infrastructure to
look for an embedder specific file and if present allows its contents to
override anything set in runtime_enabled_features.json5.

I've included a few examples of how this would work in
runtime_enabled_features_valid.override.json5

I've also confirmed that if a feature is configured the override file,
that the tests inherit this behavior.

e.g. I changed CSSScrollTargetGroup in the overridden file to set the
status to experimental. This resulted in expected test failures:
https://ci.chromium.org/ui/p/chromium/builders/try/linux-rel/b8709621089823682465/test-results?q=ExactID%3Aninja%3A%2F%2F%3Ablink_web_tests%2Fvirtual%2Fstable%2Fwebexposed%2Fcss-properties-as-js-properties.html+VHash%3A32f081785efe9631&clean=

Bug: 428882127
Change-Id: I5b5f79aae74c9f43f19fd79db0e3dc86774b83c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6731644
Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Mike Jackson <mjackson@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1489092}
19 files changed
tree: 7aa6925c9dc7c39ba86a39bb3fd320ed1a1decfd
  1. .github/
  2. agents/
  3. android_webview/
  4. apps/
  5. ash/
  6. base/
  7. build/
  8. build_overrides/
  9. buildtools/
  10. cc/
  11. chrome/
  12. chromecast/
  13. chromeos/
  14. codelabs/
  15. components/
  16. content/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia_web/
  23. gin/
  24. google_apis/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. net/
  33. pdf/
  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. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .cursorignore
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. 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.