Google Git
Sign in
chromium / chromium / src / 87f02c7d965fd922e4aed1544e6cba231be481da
commit87f02c7d965fd922e4aed1544e6cba231be481da[log] [tgz]
authorYoshisato Yanagisawa <yyanagisawa@chromium.org>Thu Jan 27 05:29:26 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 27 05:29:26 2022
treeef4df191d218259bd6e1c2ff0dfa2fb0aa2b5901
parentcef92800c716968e1e2acaa2053772e255402b72 [diff]
Make fenced frame's COEP test not depend on KEYS.

We used to use KEYS stored in resources/utils.js to look up the UUID.
However, it always make me wonder if tests may pass unexpectedly due to
typo on key names.  When we pass the token from the testers, we do not
need to worry for key name typos in the testers.

In addition, we created a embedder-policy.js to share the setup
function with tests with the COEP header and without the COEP header.
We also unified the embeddee HTML file because the file became
identical.

Bug: 1277430
Change-Id: I182c53f5c28d9f3c082daae45687f5f76f26a7dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3396406
Auto-Submit: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Cr-Commit-Position: refs/heads/main@{#963898}
9 files changed
tree: ef4df191d218259bd6e1c2ff0dfa2fb0aa2b5901
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.