
To measure PDF Searchify's success in increasing user interaction with PDFs and to show Searchify progress (see go/pdf-ocr-design, page 8), the following two states are passed to the PDF Viewer WebUI: - PDF has searchify text. - Searchify is in progress. The former will be used to record the new metrics and the latter will be used to show Searchify progress indicator. Bug: 360803943 Change-Id: I08bc59813b0ec1718df3475dc1a6ad8b1519b34c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6001955 Reviewed-by: Lei Zhang <thestig@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/main@{#1380199}
//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.