commit | edf90f28db3c398ca7f71f3eb2e5143279f56313 | [log] [tgz] |
---|---|---|
author | Rafał Godlewski <rgod@google.com> | Thu Jun 05 15:27:39 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 05 15:27:39 2025 |
tree | 8defd7fbb4fee9bccf672386f63f1d64a629c620 | |
parent | ad47b9c495304371131678d26b2340a3b6353425 [diff] |
Reland "[iOS] Enable kSyncTrustedVaultInfobarImprovements in tests" Patchset 1 contains the original commit. The modified tests are enabled on the simulator only, this CL updates the `isRunningTest:@selector` to take that into consideration. Ran it on ios-device to confirm it compiles. This is a reland of commit e96202b505db42f7e6684120ba8dadb994bf1f4e Original change's description: > [iOS] Enable kSyncTrustedVaultInfobarImprovements in tests > > This CL is in preparation for adding a fieldtrial for the feature > (https://crrev.com/c/6578421). With the feature enabled, tests that load > a sign in page with a sync error have to handle infobar error being > displayed. > > Bug: 413671967 > Change-Id: I8f20d6e44b6bcfe110083568581300875a8e24e4 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6606174 > Reviewed-by: Vincent Boisselle <vincb@google.com> > Commit-Queue: Rafał Godlewski <rgod@google.com> > Cr-Commit-Position: refs/heads/main@{#1468130} Bug: 413671967 Change-Id: I15afc62d006fffacfafd66b70534615b1447e067 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6615241 Reviewed-by: Vincent Boisselle <vincb@google.com> Commit-Queue: Rafał Godlewski <rgod@google.com> Cr-Commit-Position: refs/heads/main@{#1469966}
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.