4 Replies Latest reply on Oct 10, 2014 7:41 AM by LuxSci

    Launch Reader from PDF file in Google Chrome browser PDF viewer

    LuxSci Level 1

      Hello!

       

      So I have a fillable PDF form which runs document level JavaScript to essentially render itself inactive (hides fields, etc.) if opened in anything other than Reader or Acrobat. This works great, especially in Google Chrome has known problems with submitting fillable PDF forms properly.

       

      Here is an example form: https://luxsci.com/forms/6296/2251/Qlg5/Medical_Center_Intake_Form.pdf

       

      Open in Chrome and it's unusable, there's a warning layer, and a JavaScript alert. Open in Reader or Acrobat and it renders fine and submit works great.

       

      When the file is downloaded in Chrome it's saved locally, i.e. Chrome displays the file URL as: file:///C:/Users/David/Downloads/Medical_Center_Intake_Form%20(3).pdf

       

      I am trying to make the process of opening the file from Chrome in reader as simple as possible for the end user. As such, I am wondering if there is a way to add a button which will launch Reader on the end-user's desktop/laptop and open this file?

       

      Any advice would be greatly appreciated!


      Thanks!

        • 1. Re: Launch Reader from PDF file in Google Chrome browser PDF viewer
          gkaiseril MVP & Adobe Community Professional

          Not surprising for a 3rd party product to have that issue.

           

          Have you searched to see how to make Adobe Reader or Acrobat the default PDF viewer for Chrome?

           

          You should note that FireFox has similar issues.

           

          Configure browser to use the Adobe PDF plug-in

           

          Adobe PDF plug-in

          • 2. Re: Launch Reader from PDF file in Google Chrome browser PDF viewer
            LuxSci Level 1

            Thanks for your comments, but that isn't the issue. We provide form processing services and have developed an effective workaround via document level JS to render the form unusable and non-submittable (is that a word?!) if opened in anything other than Adobe Reader or Acrobat. The complaint we are trying to deal with is that non-tech savvy users can't figure out how to open the PDF in Reader when Chrome auto opens it for them in the built-in broken Chrome PDF viewer.

             

            While I could certainly provide instructions for how to install/enable the Adobe Reader plugin in Chrome, the point is to avoid requiring the non tech savvy end-user to do anything other than click a button to open the file in Reader. So asking them to install/configure the adobe PDF plugin in their browser is not a feasible solution. So what I want is this:

             

            -PDF opens in Chrome's built-in PDF viewer and user sees notice that they can't use the form in the current program.

            -User can click a button saying "Open this file in Adobe Reader"

            -Clicking the button launches the local computer's Reader application, and opens the file. The PDF is then rendered normally and can be filled out and submitted as normal.

             

            I don't really think it's possible because of browser security restrictions against launching executables, but since the browser is just showing an embedded locally downloaded PDF file, I thought maybe there's a way...

             

            Thanks!

            • 3. Re: Launch Reader from PDF file in Google Chrome browser PDF viewer
              Bernd Alheit Adobe Community Professional & MVP

              LuxSci wrote:

               

              I am trying to make the process of opening the file from Chrome in reader as simple as possible for the end user. As such, I am wondering if there is a way to add a button which will launch Reader on the end-user's desktop/laptop and open this file?

              Not possible.

              • 4. Re: Launch Reader from PDF file in Google Chrome browser PDF viewer
                LuxSci Level 1

                Great, thanks for confirming Bernd, I appreciate it!