Browsers and LoopLink

Thursday, April 7, 2011

Internally we argue about which is the best browser. For us, we argue between two: Firefox vs. Chrome but we understand a good portion of our users are still in IE as well.
According to our Google Analytics our users' preferences break down like this:

Browser % of Users
Internet Explorer

We could write volumes about IE and why it drives us nuts to work with but nobody wants to read through that much geek speak. Suffice it to say that we do our best to deal with IE and all of its... "quirks" but if we had our way, everyone would be using Firefox or Chrome.

For us, IE is highly unpredictable in how it interprets our page layouts and is just not as quick at running JavaScript as the other two. This is why we advocate for users to run LoopLink in Firefox or Chrome.

Both are excellent browsers that have proven to be highly predictable in how they display LoopLink but recently we have had some issues with the Google Chrome PDF viewer. It seems saving PDFs (i.e. project summaries) doesn't want to work in the native viewer.

So for the 11% that side with Doug on this argument (GO CHROME!) here is a quick run through on how to get Google Chrome to go back to using the Acrobat Plug-In we all know and love.


  1. Type in the address bar.
  2. Find the Chrome PDF Viewer plug-in and disable it.
  3. Find the Adobe Acrobat plug-in and enable it.

Disabling the Chrome PDF viewer is supposed to automatically enable the Adobe Acrobat Reader but we haven't had great luck with that. Either way its a pretty quick and easy thing to do.

We will keep an eye out for an update to the Chrome PDF viewer and let everyone know as soon as they get the save function working better.

Article Update (4/25/2012)

So, we weren't very flattering to IE in this original post but we have to say, Internet Explorer 9 has really come a long, long way towards predictability. Hats off to Microsoft for bringing things this far forward. There are still some bugs, one that kind of gets in the way of LoopLink but it is no worse than the Chrome/Acrobat PlugIn issue described in the original post. Overall the newest IE is light years from the previous versions and we are looking forward to seeing what comes next.

The save option from the Chrome PDF Viewer is still buggy for us. You can either maintain the solution listed above or, you can use the print function and print the file to a pdf.