a6b442e03f
Use the GetPDFiumPageForTest() helper in more places, instead of calling PDFiumEngine::GetPage() directly. Then do less checks to make sure the page in non-null, as GetPDFiumPageForTest() does it already. Change-Id: I476ed3a07d626c448a7373744ad6927ff6d144f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5906784 Reviewed-by: Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1364045}
//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.