[Extensions Cleanup] Move creation of tab-based ports to factory method ExtensionMessagePorts can be created for tabs, extensions, or a specific endpoint. The latter two have separate factory methods, but the former uses a special constructor. This is confusing, since it's inconsistent and that constructor should only be used to construct tab-based message ports. Clean this up by making that a factory method. This CL has no behavior change. Bug: None Change-Id: Ief8d356bf8d396f37c6bc3131ff7b2676a54c9d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6143725 Auto-Submit: Devlin Cronin <rdevlin.cronin@chromium.org> Reviewed-by: Kelvin Jiang <kelvinjiang@chromium.org> Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org> Cr-Commit-Position: refs/heads/main@{#1403274}
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.