17

A video would be helpful indeed.

    Merged 3 posts from PDFs require reload to display.

      Would it be possible @SkullEnemyX, @Boot, or @HatshibaInu, to share debug information when this occurs? I'm having trouble reproducing it on my end. What I'm looking for is console logs, which can be retrieved like so:

      1. In the Develop menu, enable Show Console Errors Indicator.
      2. Trigger the bug by opening up a PDF page
      3. You will likely see a red circle with a "!" character next to the Refresh "↻" icon. Tap that button to open the console.
      4. Share a screenshot of the errors that are shown.

      Thanks very much!
      -nano

        20 days later

        I'm experiencing the same issue, so I thought I'd share my console error screenshot:

        URL: https://arxiv.org/pdf/2302.12173.pdf

        The PDF loads fine if I then press the reload button after that, although the errors are still present. There are also console warnings, but I've hidden them for the screenshot below.

        Version 0.99.124.4.1-beta (WebKit 616.1.14.11.1)
        MacBook Pro (macOS Ventura 13.4 build 22F66)

        Hope this helps with the troubleshooting. I'd also want to take the chance to express my thanks for the shift to PDF.js, it's more feature-filled than the older PDF viewer, and has been very useful to me.

          14 days later

          Steps to reproduce:
          Click on https://www.africau.edu/images/default/sample.pdf.

          Expected behavior:
          The PDF should show in the browser like in Safari (
          However, in Orion, it looks like this:

          Orion, OS version; hardware type:
          Version 0.99.124.4.1-beta (WebKit 616.1.14.11.1)
          MacBook Pro 13", 2020, Intel (macOS Ventura 13.4 build 22F66)

          • Vlad replied to this.

            adamaveray
            Yes indeed! It seems to be the same issue as I am able to see the PDF after refreshing. Thank you for sharing this temporary solution!

              Merged 4 posts from PDFs not showing.
                5 months later

                Just jumping in to say I'm having the exact same issue as others described here. Otherwise enjoying using Orion but this is frustrating. Particularly, as other commenters note, when downloading large PDFs, or from a slow server, or via a series of redirects. I've also noticed this issue when PDFs have been previously loaded on an inactive tab, and when I switch back to it, the page is blank. This is especially frustrating if you are, like I am right now, in and out of internet access.

                I'm used to downloading PDFs and not viewing them in browser. If this is not yet resolved I would appreciate the option to treat PDF links as a download and not default to opening them in browser. (though I suppose I can just revert to 'download as' pdf links, but that isn't possible with indirect links)

                • Vlad replied to this.
                  9 months later

                  still this issue persists,
                  i have "Enable PDF.js viewer" enabled by default. i tried disabling that and opening the pdf webpages then the browser completely frozen and crashed.
                  I then enabled the "Enable PDF.js viewer", but the same issue like empty blank screen when opening a pdf webpage, page is opening only after refreshing it.

                  orion version: Version 0.99.128.2.1-beta (WebKit 619.1.11.111.2)
                  machine: Macboook Pro M3 Pro, 18GB RAM.

                  • laiz replied to this.

                    Wasn't there a similar issue on which I had commented with the same problem? maybe a merge is in order.

                    • laiz replied to this.

                      laptudirm #7450 was an issue for everyone using that particular rc build, this report is about something more inconsistent.

                        Reposting my findings here:

                        if you open the console after opening the link (when its still blank) the console shows errors

                        after the reload, these errors remain:

                        Comparing with the errors for people who didn't need to reload the viewer, after the reloads the errors match up, but before the reload there are those unhandled promise rejections which aren't experienced by people who don't have this bug.

                          4 months later

                          • Yyee

                          • Post #26

                          still fails to load PDF with latest Orion RC