48ba13db87
Make the behavior in this scenario more consistent with other apps. Change PdfInkModule's to remember if it ever received a pen event, and ignore touch events after that. Update tests with the new expectations, add ApplyStrokeWithTouchAtPointsNotHandled() as needed, and remove the now fulfilled TODOs. Bug: 392650039 Change-Id: I38c45d8fc369748c49619e3448f713651e5e3797 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6216548 Commit-Queue: Lei Zhang <thestig@chromium.org> Reviewed-by: Alan Screen <awscreen@chromium.org> Cr-Commit-Position: refs/heads/main@{#1413686}
//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.