Google Makes Latest Chrome Build Open PDFs By Default
An anonymous reader writes "Google is changing the way its browser handles PDF files, starting with the Chrome Canary channel. Citing security concerns, the company wants Chrome to open PDF files by default, bypassing any third-party programs such as Adobe Reader or Foxit Reader."
Great. Another configuration change to manage on all our workstations.
The Chrome PDF viewer is shit. So is the Firefox one. They're fine for viewing most basic PDFs, but anything more involved (forms, interactive PDFs, portfolios, etc.) and they both just shit the bed.
On older laptops - those that reasonably work well only with XP, I not only install Chrome as the best performing browser, but I also advise people to use it to view PDFs. Note that viewing a PDFs is very different than filling it out etc. A viewer needs to be simple and well performing, and in my experience, even on 10+ year old hardware, Chrome shines there. So, for one, I do welcome this change.
A successful API design takes a mixture of software design and pedagogy.
bypassing any third-party programs such as Adobe Reader or Foxit Reader
Technically, Adobe Reader is the first-party program and Chrome is the third-party program for reading PDFs.
Laughter is the Spackle of the Soul.
For that matter QNX, a complete graphical OS including essential programs like a web browser and even a web server is a couple MB - smaller than many odd DOCUMENTS.
I wonder how blazingly fast a 4MB OS is on 4GHz machine with GBs of RAM. The CPU could process the entire OS in less than a millisecond.
Likely this was done to be consistent. Any security the Chrome PDF viewer could offer could be easily bypassed by an attacker forcing the file to download. If the user clicks it, it opens in the system PDF viewer.
I believe Adobe Reader has its own sandbox so this might seem a bit weird... but at least one thing Chrome has going for it that Reader has not is that Chrome is more likely to be up-to-date (I forget how Reader updates itself, if it does at all) AND it pulls the latest Chrome PDF plugin with it.
When I set a default for a file extension in the OS, I expect the browser to respect that setting. Both Firefox and Chrome are now "bad apples" in the desktop configuration arena. Shame on them both. I see no reason why their implementation would be any more secure than the applications I've already chosen.
I do not fail; I succeed at finding out what does not work.
And you're the only one who came.
Laughter is the Spackle of the Soul.
chrome://plugins/
Chrome PDF Viewer --> Disable.
That's completely opposite of my experience.
On my not-so-hot computer I regularly open very complex, 400+ page PDFs (music scores mostly). We're talking 30MB w/o any imbedded images, just pure intensive processing instructions.
Chrome, from a total standstill (the process not even running yet), takes just slightly longer then it takes me to blink to start, load the PDF, and render. It's an order of magnitude faster in every way then every other PDF viewer I've tried, and I've tried quite a few.
It lacks features (PDF bookmarks, etc), but render speed is fantastic.
My
Back in reality, this will stop a large number of infections from occurring.
how can a document renderer, basically a postscript web browser with ALL THE FUNCTIONS REMOVED, be bigger than an virtual computer in your computer?
Ah.... what you are missing is clear now. You missed the point that a PDF viewer is a virtual computer in your computer.
Among other things.... PDFs can contain scripts and various executable bits. What do you think the major source of security issues in PDF is?