Store interop parameters in auxiliary data structures Instead of assuming that various operations happen in order. Since each interop event has a unique time, this makes it easier to ensure that the correct response is associated with each event. Without this, there is the possibility of a race condition between the asynchronous registration handling from the data host manager and the storage-sequence task. This will make it easier to support redirect chains in interop tests without flakiness. Bug: 330555387 Change-Id: I78892ba7d2a8bfdfcf7540c95727386c2a8d29ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5402806 Reviewed-by: Nan Lin <linnan@chromium.org> Commit-Queue: Andrew Paseltiner <apaseltiner@chromium.org> Cr-Commit-Position: refs/heads/main@{#1279161}
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.