`doc.internal.pageSize.getWidth()` doesn't match measured value

function pdf() {
  const { jsPDF } = window.jspdf;
  const doc = new jsPDF("p", "px", "a4");
  const pageWidth = doc.internal.pageSize.getWidth();
  console.log("pageWidth", pageWidth);
  
  doc.save("pagesize.pdf")
}

You can run the above code here: https://jsfiddle.net/6htnzja8/1/

Running the example code and looking in the console jsPDF says the page width is 446.46 pixels. If I take a screenshot of the generated PDF and measure the size it’s actually 793 pixels wide.

I think the value reported by jsPDF is wrong. Is it, or am I misunderstanding something?

[iron2414]

Is this still working? I am using jsPDF 2.3.1 and trying to put images inside a pdf, but they get blurry. When i try to enable “px_scaling” mentioned here, and https://github.com/MrRio/jsPDF/blob/master/HOTFIX_README.md the code won’t compile. After checking the package, there is no “hotfix” in the code, and the jsPDF constructor only takes “jsPDFOptions”

  export interface jsPDFOptions {
    orientation?: "p" | "portrait" | "l" | "landscape";
    unit?: "pt" | "px" | "in" | "mm" | "cm" | "ex" | "em" | "pc";
    format?: string | number[];
    compress?: boolean;
    precision?: number;
    filters?: string[];
    userUnit?: number;
    encryption?: EncryptionOptions;
  }

Edit: I had to pass it in as a constructor parameter, and surpress the statement with // @ts-ignore. It works now properly.

[HackbrettXXX]

Yeah, for myself and for future reference, I did the math once again:

96px = 1in (css pixels)
72pt = 1in   (PDF 1.3 specification)

-> 96px = 72pt
-> 1px = 72/96pt

Which means we have to multiply each pixel by 72/96 to get pt. So the scaleFactor of 72/96 is correct and one has to enable the hotfix in order to get the correct scaling for pixels. We should really document that the hotfix is required for the px unit and make this the default with the next major release.

Thanks for bringing that up 😉