90784b92f4
Instead, have PDFiumFormFiller talk to PDFiumEngine, whose client delegates to PdfViewWebPluginClient. PdfViewWebPluginClient can then talk to the WebFrame to get the per-frame isolate. While this removes blink::MainThreadIsolate() usage in production code, the newly added GetIsolate() method needs to be implemented for unit tests to pass. This CL adds two new test-only blink::MainThreadIsolate() calls for now. Change-Id: I304eda857803616351056dfada21e1d869d0754b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5091351 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1243013}
//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/1220865): Remove existing //content dependencies.