
A user can simultaneously apply different modes of input (such as mouse + keyboard, or mouse + touchscreen) to cause a change in tool state in the middle of a drawing stroke. Add a test for changing the drawing brush type in the middle of an in-progress stroke, such as from the pen to the highlighter. This causes the entire stroke to change with the updated state, which is not the desired behavior. Bug: 381908888 Change-Id: I908c252d7b08868a277e96bb2673fd7661fea088 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6115082 Reviewed-by: Lei Zhang <thestig@chromium.org> Reviewed-by: Andy Phan <andyphan@chromium.org> Commit-Queue: Alan Screen <awscreen@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1399470}
//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.