0
Files
src/pdf
Alan Screen bac0a0770b [PDF Ink Signatures] Account for device scale in Ink zoom
PdfInkModule relies upon a client query to know the scale factor to
apply when transforming points.  This has included the zoom factor
within the PDF viewer plugin, but has been missing any extra screen
scaling for OS-level display scaling.  HiRes on some macOS devices or
Windows devices with display scale settings set to something other than
100% could cause a significant shift in stroke placement.

Update the PdfViewWebPlugin::PdfInkModuleClientImpl to incorporate the
device scale when providing zoom for Ink strokes.

Bug: 378623808
Change-Id: Ic4bc2b89eaa0de99d38345249552986e9aeb17f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6017318
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Alan Screen <awscreen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1382514}
2024-11-13 19:30:56 +00:00
..
2024-09-18 14:23:33 +00:00

//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.