fcac55e848
Adds "enable_ppapi" guards around PPAPI-dependent code in ChromeContentClient. Note that this change does not touch uses of PepperPluginInfo that are satisfiable with a forward declaration. Also removes the ShouldAllowPluginCreation() override from ChromeContentBrowserClient, rather than guarding its use of PepperPluginInfo. This override only was used for the PDF viewer's Pepper plugin, and the PDF viewer no longer uses a Pepper plugin. Also fixes some IWYU issues related to webplugininfo.h. Bug: 1306610 Change-Id: I688db8b879218f3793702a4dc9c1c3cd11f4c1d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3764725 Reviewed-by: Lei Zhang <thestig@chromium.org> Commit-Queue: K. Moon <kmoon@chromium.org> Cr-Commit-Position: refs/heads/main@{#1024529}
//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.