Defer system calls in PrintingContext for OOP printing The PrintingContext class contains a mix of application state information and calls to OS system APIs. The application state information needs to remain tracked in the browser process. When out-of-process printing is enabled then the system calls need to be made over in the Print Backend service. Introduce a PrintingContext control member for indicating if system calls should be skipped. When set this would be applicable for PrintingContext objects in the browser when OOPPD is enabled, so that only the needed application state information is maintained. When not set then it would be applicable for legacy in-browser printing or for a PrintingContext operating in the Print Backend process, when making OS system calls are appropriate to happen. Bug: 809738 Change-Id: Icb42e1659ac1615fbba4779cd572b9e4058810ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3179530 Reviewed-by: Raymes Khoury <raymes@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Commit-Queue: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/main@{#945042}
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.