commit | cfbec794ae5768a446fc71185e63f2e1dba2f4ee | [log] [tgz] |
---|---|---|
author | Alan Screen <[email protected]> | Wed Dec 23 22:00:37 2020 |
committer | Chromium LUCI CQ <[email protected]> | Wed Dec 23 22:00:37 2020 |
tree | a7e66dff03e97bfb50a564afaa443dbbae756ee0 | |
parent | 2c41324f0b6f5c9b9dc714f656624731249ed3dc [diff] |
Relocate printer capabilities Printer capabilities have been located under //components since r540621, when they were moved here in anticipation of the upcoming printing backend service. However, once it came time to introduce the service it landed under //chrome, because of the guidelines required to add it to //components were not satisfied. [1] One ripple effect of the service landing under //chrome is that printer capabilities need to also be moved out from //components. Its presence under //components results in a dependencies conflict for Mac because it ends up causing a dependency on //content/browser, which is not allowed. [2] Since printer capabilities are referenced by only one space, [3] resolve this by moving printer capabilities code out of //components and into a home under //chrome like where the service is. [1] https://source.chromium.org/chromium/chromium/src/+/master:components/README.md [2] https://source.chromium.org/chromium/chromium/src/+/master:chrome/BUILD.gn;drc=98fd3773af40462359d2cef844f946526e99b1fe;l=1301-1305 [3] https://source.chromium.org/chromium/chromium/src/+/master:chrome/browser/ui/webui/print_preview/ Bug: 809738 Change-Id: I50d76e18f6e86f6bf483883c1d0654c8fc0724d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592628 Commit-Queue: Alan Screen <[email protected]> Reviewed-by: Rebekah Potter <[email protected]> Reviewed-by: Nico Weber <[email protected]> Cr-Commit-Position: refs/heads/master@{#839188}
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.