db66dce79f
Since the eraser tool erases entire strokes on contact, there is less of a need to have different eraser sizes. Remove eraser size support in its entirety: - Change the frontend code so the eraser tool has no options. - Remove associated icons and constants. - Update tests to match frontend behavior changes. - Change the backend code and remove all configurable eraser sizes: - Add a default eraser size. - Update/remove tests that assume the eraser size can change. - Remove histogram for eraser size. NO_IFTTT=False alarm Bug: 378143561 Change-Id: I071977596ee029f6bd05c714b6a23b361309b1ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6300545 Reviewed-by: Alan Screen <awscreen@chromium.org> Reviewed-by: Andy Phan <andyphan@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1424711}
//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.