commit | ecd384fa19ececdf6ad57cddfdbe01052dd6e44c | [log] [tgz] |
---|---|---|
author | Colin Blundell <blundell@chromium.org> | Wed May 11 08:58:30 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 11 08:58:30 2022 |
tree | 1bdfb8662e1d5ae3ccbee9d5dc67671224b91b37 | |
parent | 3a96431b4fe4a284f243ca0669f07aed5bbc5e64 [diff] |
[DOMMessageQueue] Convert content_browsertests to preferred constructor This CL converts the remaining usages of the DOMMessageQueue default constructor in content_browsertests to the one that takes in a WebContents instance. The former listens for messages from all WebContents instances via a notification, while the latter observes the passed-in WebContents instance to listen for messages from that instance. We are trying to eliminate the former entirely as part of the elimination of NotificationService. The conversions are for the most part straightforward; the one exception is site_per_process_unload_browsertest.cc, in which we need to catch a WebContents instance created via a popup to be able to listen for messages that occur in that instance. Bug: 1174774 Change-Id: Ieaf7d2811282e2a3c0c7dbbe95c58d2c7aeff20c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3635781 Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1001976}
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.