commit | 0c0be9c4711f074ea340224cdc10ddf73ab31c0c | [log] [tgz] |
---|---|---|
author | Matt Menke <mmenke@chromium.org> | Fri Dec 03 22:25:02 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 03 22:25:02 2021 |
tree | 6d6eba0bcf24c6ae1c31eae6697c062ec4591d50 | |
parent | 4956b9aaafde4a4e7d8a794b62f23de28d2e1e02 [diff] |
[FLEDGE] Replace InterestGroupFencedFrameBrowserTest.TopFrameHostname. Replace it with a test that just runs an auction in an iframe and loads the result in a nested fenced frame. InterestGroupBrowserTest.TopFrameHostname already gives us plenty of coverage that the top frame hostname is correct, and we don't really need a FencedFrame variant of it. What the fenced frame variants was really after was just checking that loading an auction winner in a fenced frame in an iframe works, so just do that instead. InterestGroupFencedFrameBrowserTest.TopFrameHostname was running into failures on the bots, likely due to the number of processes it was creating. Only testing one case, and using less nesting, should hopefully resolve that. Bug: 1259733 Change-Id: Ie254961f7c820fd686084b197480c49ba86d2478 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3311078 Reviewed-by: Caleb Raitto <caraitto@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/main@{#948196}
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.