dce2e585ba
This new policy is to provide an optional control on the resolution used when rasterizing a PDF to images. This happens when using the Print to image option in Print Preview. The Print to image option is always available on Linux and ChromeOS, and is available on Windows and macOS via the PrintAsImageAvailableForPdf policy. This equates to all of the platforms for which Print Preview is enabled. The policy specifies an integer for the DPI to rasterize to. Without this policy the printer specific or system default (depends upon OS) resolution will be used. A non-positive resolution value would be nonsensical, and behaves the same as if the policy were not even present. This enables administrators to choose a resolution to be used with print rasterization that balances image quality with printing speed that is acceptable for an organization. TESTED=Manually on Windows by setting a registry DWORD value for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Chromium\PrintAsImageAvailableForPdf and also setting a registry DWORD value for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Chromium\PrintRasterizePdfDpi and manually tested for ChromeOS on Linux with policy file placed in /etc/chromium/policies/managed Bug: 1233149 Change-Id: Iefbb6814030124adfe885e0e90847fe26f1ddffa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3084502 Commit-Queue: Alan Screen <awscreen@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Reviewed-by: Owen Min <zmin@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#911490}
//printing contains foundational code that is used for printing. It can depend
on other low-level directories like //cc/paint and //ui, but not higher
level code like //components or //content. Higher level printing code should
live in //components/printing or the embedder.