9c36c864d1
Add a simpler way to create a PDFiumRange that represents all the text on the page. Make callsites easier to read and more foolproof. Change-Id: I7271940e5f2da7271c097df121b52affa63061ca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5886131 Reviewed-by: Alan Screen <awscreen@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1360000}
//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.