When printing a PDF on a Android chrome, only the first page will be printed

[LgnMs]

I find this code, I think Android needs a delay of 1500ms yet.

// pdf_print_service.js

performPrint() {
    this.throwIfInactive();
    return new Promise(resolve => {
      // Push window.print in the macrotask queue to avoid being affected by
      // the deprecation of running print() code in a microtask, see
      // https://github.com/mozilla/pdf.js/issues/7547.
      setTimeout(() => {
        if (!this.active) {
          resolve();
          return;
        }
        print.call(window);
        // Delay promise resolution in case print() was not synchronous.
        // modified by ngx-extended-pdf-viewer #83
        const isIOS = navigator.platform && [
          "iPad Simulator",
          "iPhone Simulator",
          "iPod Simulator",
          "iPad",
          "iPhone",
          "iPod"
        ].includes(navigator.platform)
        // iPad on iOS 13 detection
        || (navigator.userAgent.includes("Mac") && "ontouchend" in document);

        setTimeout(resolve, isIOS ? 1500 : 20); // Tidy-up.
        // end of modification by ngx-extended-pdf-viewer
      }, 0);
    });
  }

[stephanrauh]

@KillerCodeMonkey I'm not sure if you're using Android, but it's worth a try... are you aware of any print problems with Android? Should I increate the delay, like I already do for iOS?

[manubauer]

I am facing the same issue on macos with chrome - only the first page shows up.
Package version 18.1.14

[KillerCodeMonkey]

@stephanrauh tested in chrome and firefox for android and i can confirm that only the first page is rendered in chrome, but it is working in firefox :).

EDIT: Tested chromium based Brave and there it only prints the first page as well.

[stephanrauh]

@manubauer Can you test if the showcase prints correctly on your machine? I bet it's a CSS issue in your case. I've tested it a few seconds ago, and I see all 333 pages of my test document.

[KillerCodeMonkey]

@stephanrauh it seems that the pdf viewer is trying to print the wrong dom node, when using inside a dialog or something similar.

on your demo page (simple demo). it does not print the pdf, when using the print button on Android Brave Browser.

Same happens in my app, where a pdf is shown in a dialog/modal. It prints the page body below.

In the demo it prepares very long all >300 pages, but this is the preview

But it is working in Firefox based browsers.

[stephanrauh]

@KillerCodeMonkey I didn't expect that behavior. It feels like a hot trace!