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}
29 files changed
tree: a7e66dff03e97bfb50a564afaa443dbbae756ee0
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

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.