557a290a77
Delete all the code in //pdf/ink, which includes the Ink stub, and switch over to the Ink library directly. Temporarily disable a PdfInkModuleStrokeTest that is now failing, as the Ink library behaves differently from the stub. The test case will be fixed separately in the next CL in chain. Bug: 339682315 Change-Id: I45464ebbd4a4025ab31bd775007abf4e64ac1f3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5867108 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Andy Phan <andyphan@chromium.org> Reviewed-by: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1357069}
//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.