Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
..
public 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
BUILD.gn 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
DEPS 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
DIR_METADATA 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
OWNERS 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
README.md 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
ipc_flow_diagram.png 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
print_compositor_impl.cc 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
print_compositor_impl.h 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa
print_compositor_impl_unittest.cc 4762b62e7d Publish DEPS for 106.0.5249.13 1 anno fa

README.md

The print_compositor service should composite multiple raw pictures from different frames into a complete one, then converts it into a print document format, either PDF or XPS. This all happens within an isolated sandboxed process.

While the compositor creates single-page PDF objects it can optionally collect those into a multi-page PDF or XPS document object. Otherwise a multi-page PDF document is made by sending an extra multi-page metafile which contains repeats of each of the previously processed pages all in one larger message.

Message flow when interacting with the print document compositor is as follows:

IPC flow for print compositor
usage