Ken: Well, given that it’s on the most untested testing release channel of Chrome, yes, I’d call it a test, both technically and to see how much blowback it would generate. As someone remarked, Google does think they know what’s best for everyone, and though their batting average isn’t a thousand on that front and some of the things they do can really sting, they are correct an impressive amount of the time. That’s the super-bleeding edge channel, and between it and stable there are two other channels it would have to make its way through, during which time it could be improved somehow or the idea could be scrapped. Note that this is only lit up in Chrome Canary now. Like getting rid of NPAPI, which Mozilla is also doing, this will probably make the web more secure in general, won’t it? How many answers to the question in the title do you need?Īs I understand it users have the option to open the downloaded PDFs using whatever they want and as the author pointed out this can be reverted.
Chrome change pdf viewer pdf#
Acrobat has a long history of major vulnerabilities and it’s one more thing users and sysadmins have to stay on top of, meanwhile the source code to Acrobat may be in the wind due to their own internal security failures.Īdditionally, you’re already running Chrome, why launch another piece of software to read a PDF and create another vector of attack if you don’t have to. Sure PDFs are important and have to look just right, but so is an up-to-date secure reader inside of Chrome which I’ll speculate is more effective by a longshot at updating than Acrobat. I’m unclear why this isn’t obviously a good idea: For most people and most PDFs, Chrome’s reader is good enough. Once after giving the file name a name in the Windows dialogue, and when the PDF creator launches, it asks for the file name again plus a lot more information some of which is already filled in with the current date or embedded info from the file or site you are printing from. Plus Chrome can now save in PDF format, so I don’t need to load in a 3rd party PDF Cloud printer (PDF Creator by ), which is great for all other Windows programs but the save dialogue looks more like we’re sending a fax (filename, author, date, subject, notes….) and happens twice. Not worth the 18% of memory required to keep the pre-launcher running. Their pre-launcher only reduced PDF loading time by 25%.
Chrome change pdf viewer update#
My beef with Adobe is after each update it always insist on leaving a pre-launcher loaded into memory. I don’t mind the in browser viewer in Chrome as I’ve deleted Adobe PDF viewer in favour of the PDF Architecture by that way when I read PDF’s I have the option of editting or re-organizing them if I choose to save them.