3a745b822c
The PDF displayed in Print Preview should reflect what is being sent to the printer and should not be modified by Searchify. The minimal PDF Viewer that displays the preview is also not capable of displaying Searchify's UI. Thus it raises JS errors when Searchify tries to ask it to. Add a PDFiumOnDemandSearchifierTest case to show this CL stops Searchify in Print Preview. To do so, enhance SearchifierTestClient to be able to tell PDFiumEngine that it is in Print Preview mode. Along the way, encapsulate SearchifierTestClient. Bug: 405433817, 406530484 Change-Id: I535ece9beb7429a4844c3310add52bc5fd6f1952 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6405712 Reviewed-by: Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1439561}
//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/40186598): Remove existing //content dependencies.