be826009de
Once a print job starts making the system calls to print the document, the PrintingContext can possibly get a non-zero job ID. Whatever the ID value is, that is passed along through the print notifications stack in the browser process. This is of particular importance for ChromeOS, which uses the job ID value for extra job management. Update TestPrintingContext to support using a particular job ID once the NewDocument() call is invoked. Expand the printing tests to use this and capture the job ID once the document is done. This is used as part of validation checks, demonstrating that the value is incorrect when the out-of-process print drivers feature is enabled. Bug: 1518019 Change-Id: I695bc352f14f0e85327ef9f20fa7b7b4361e9fb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5208090 Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1249762}
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.
If you found a bug, please file it at https://crbug.com/new.