d824ce06dc
Call pp::PDF::Print() synchronously in the Pepper viewer, instead of posting a task to the main thread. The old implementation was an artifact of the days when the PDF plugin was in-process and re-entrancy was a risk. But now that the plugin is out-of-process, pp::PDF::Print() already invokes the print dialog asynchronously across the process boundary to the renderer. Change-Id: Iabc0dcfc561492353cb666ad6569059e52d87ed6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2964274 Commit-Queue: Daniel Hosseinian <dhoss@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/master@{#894043}
//pdf contains the PDF plugin, its Blink-based replacement, as well as PDF
utility functions that leverage PDFium. It can use low-level components that
live below the content layer, as well as other foundational code like
//printing. It should not use //content or anything in //components that
lives above the content layer. Code that lives above the content layer should
live in //components/pdf, or in the embedder. All the code here should run in
sandboxed child processes.
TODO(crbug.com/1220865): Remove existing //content dependencies.