
Just use a single boolean variable to store the result, and reuse it in all PDFium API calls that return a bool. It is not clear what the benefit is for having 6 separate bools to keep track of results from different PDFium API calls. Change-Id: I6a707e2ee3af7708c8bc9244bbf38e926c1ee284 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5917331 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1365893}
//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.