Fix incorrect imports of blink into content & chrome Importing blink mojo types into other directories that aren't blink causes imports of internal blink header files (WTF::String/Vector/HashMap). This can then be abused by the caller to create structures that it shouldn't have access to. This is preliminary cleanup for adding an enforcement to the blink mojo header files. Change-Id: I0aa1e30f07f595023191af1c96cdf58a258dc118 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5953880 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1372961}
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.