35be0f8e3c
Currently, PDFiumPage tracks Searchified text at the granuarity of words, but the tracking gets confused after PDFiumPage::Unload() gets called, because the handles to the tracked text objects are no longer valid. Given the assumption that a PDFiumPage either only contains text from the PDF itself or only contains text from Searchify, simplify Searchified text tracking from word granuarity to page granuarity. This avoids the tracking confusion without requiring writing tags into the PDF. Bug: 376304020 Change-Id: I890b2be37ef7974b10920bc6b47126711d533d57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6223665 Reviewed-by: Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1417182}
//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.