Handle incomplete destinations in PDF documents where the viewport starts at non-zero coordinates (bug 1913617)
Hopefully this makes sense, since it doesn't appear to break "proper" PDF documents in my quick testing.
This commit is contained in:
parent
908f453384
commit
687c91d4e2
@ -1491,15 +1491,14 @@ class PDFViewer {
|
||||
height = 0,
|
||||
widthScale,
|
||||
heightScale;
|
||||
const changeOrientation = pageView.rotation % 180 !== 0;
|
||||
const pageWidth =
|
||||
(changeOrientation ? pageView.height : pageView.width) /
|
||||
pageView.scale /
|
||||
PixelsPerInch.PDF_TO_CSS_UNITS;
|
||||
const pageHeight =
|
||||
(changeOrientation ? pageView.width : pageView.height) /
|
||||
pageView.scale /
|
||||
PixelsPerInch.PDF_TO_CSS_UNITS;
|
||||
// Utilize the viewport "end-points" rather than the effective width/height
|
||||
// to avoid problems in PDF documents where the viewport starts at non-zero
|
||||
// coordinates (fixes bug 1913617).
|
||||
// NOTE: In the majority of PDF documents those values agree anyway.
|
||||
const { viewBox } = pageView.viewport;
|
||||
const changeOrientation = pageView.rotation % 180 !== 0,
|
||||
pageWidth = changeOrientation ? viewBox[3] : viewBox[2],
|
||||
pageHeight = changeOrientation ? viewBox[2] : viewBox[3];
|
||||
let scale = 0;
|
||||
switch (destArray[1].name) {
|
||||
case "XYZ":
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user