Chrome Frustrations

I’m a huge fan of Google Chrome (basically, anything Google, really).  They’re more often than not simple, straightforward tools to accomplish a wide variety of tasks.  They’re great tools for the every day user.  Google Docs is more than sufficient as a basic replacement for Microsoft Office (word processing, basic tasks in spreadsheets, even decent presentations).  Gmail is pretty awesome (supposing you don’t mind that they’re mining your email for their ad programs).  Chrome is an awesome browser.

For the most part.

I speak specifically about how Google decided that Chrome will no longer be able to use any Adobe Reader plugin: you either use a 3rd Party plugin (like Foxit) or use the Google integrated PDF viewer.  Normally, this wouldn’t be a problem, as most PDF files load perfectly fine with either of these two tools.

Lately, we’ve seen a new kind of PDF file.  It’s got the same PDF extension, but it does a very cool thing: you can embed multiple files separately into a single PDF file.  It is called the PDF portfolio.

The problem is, neither Foxit nor Google Chrome PDF plugin can render the PDF portfolio properly.  They both recognize it, and direct you to download the file and open it directly in Adobe Reader.  It’s very frustrating for me as a technician because we’re supposed to be moving to a seamless web experience.  I shouldn’t have to direct people to open another application after saving the PDF to the machine.

Furthermore, devices like Chromebooks (which can never get Adobe Reader installed) will never be able to open the PDF portfolio files.  This makes me sad.

Some come on Google.  Get with the program.  Either update your plugin or allow Adobe Reader to run in the browser again.

Please?