Google Git
Sign in
chromium / chromium / src / 629d7cb5c2029ea435d02266a86ea71ec691860c
commit629d7cb5c2029ea435d02266a86ea71ec691860c[log] [tgz]
authorLiam Brady <lbrady@google.com>Thu Dec 15 18:21:36 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Dec 15 18:21:36 2022
tree9ed4896151ed09f74baa92e421b407a06062d49c
parent909996148fa25359982aeda83e1d14e2df5ab382 [diff]
Fenced frame: Add tests for navigating nested configs

A previous CL introduced the `fence.getNestedConfigs()` API[1], and
another one allowed fenced frames to navigate configs[2]. This CL adds
testing coverage for being able to navigate nested configs created with
FLEDGE.

Updates the `generateURNFromFledge` helper function to also take in an
optional list of urls to use as the nested config urls. When set, the
urls will be read into the list of nested configs, which can be used
to navigate a fenced frame. This CL also updates the FLEDGE logic used
by the test to support component auctions.

[1]https://chromium-review.googlesource.com/c/chromium/src/+/4035572
[2]https://chromium-review.googlesource.com/c/chromium/src/+/4086678

Change-Id: I1803ff00069ab092679a10a4765b8b8cd90773da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4099227
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Liam Brady <lbrady@google.com>
Cr-Commit-Position: refs/heads/main@{#1083854}
5 files changed
tree: 9ed4896151ed09f74baa92e421b407a06062d49c
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.