3

With the experimental Enable PDF.js viewer enabled, when I click the print button within the viewer, nothing happens. With that experimental feature disable (or when using a print button not contained within the viewer) attempts to print a PDF simply bring up a blank page within the browser. Accordingly, there is effectively no way to print a PDF from within the browser other than by downloading it to my computer, opening it in Acrobat, and then printing.

Expected behavior is to be able to print from within the browser, preferably from within the PDF.js viewer.

0.99.126.3-rc (WebKit 618.1.2)

Sonoma (14)

EDIT: Upon further investigation, it seems this issue is limited to display of PDFs on certain sites, most notably outlook.office.com when previewing a PDF attachment.

  • Vlad replied to this.

    PJCville Steps to reproduce please (reproducible PDF)

        Please see the videos below:

        Steps to produce problem in Orion (Note that neither the print button within the plugin nor the default print button produces the desired result):

        Expected behavior as demonstrated in Chrome:

        EDIT: Additional video to show that problem persists in Orion even with Enable PDF.js viewer disabled:

          PJCville We'd need steps to reproduce them on our end.I s there a publi pdf on the web that exhibits same behavior?

              A quick search found this website where the same issue is duplicated. See video below:

                PJCville outlook.office.com is checking Content-Disposition headers wrongly, as the standard says filename* should be preferred if both filename and filename* are known. And unfortunately Chromium browsers are not following this at-all, all other browsers are following this

                Reference:
                https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition

                You can test same on Firefox & Safari (both will also not load PDF)

                    dino Everything works fine for me in Firefox. Safari does have the print problem within outlook.office.com, also.

                        No one is typing