Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Submission + - Is Google Poisoning PDF?

theodp writes: As much as Google is crying about Microsoft paying too much attention to the details of how its software works, one may wish that Google would learn to do the same. Especially in the case of Google Chrome's built-in PDF viewer, which the search giant imposed on users last year, quietly enabling it by default. Not everyone is thrilled with how things turned out. "I got the impression that this built-in PDF viewer was never user tested before it went live," says one unhappy camper. "I was very annoyed to find that google had hijacked my PDF settings and implemented their own viewer," complained another. "I am not able to save PDFs from my internet-banking site any more," laments a third. A "horrible piece of software," is another's take. If you can't live with acknowledged bugs and feature omissions while its engineers "try to make this better," a Googler suggests: "type 'chrome://plugins' into the address bar, find the 'Chrome PDF Viewer' and click 'Disable.'" How intuitive. So, unless some kind of licensing agreement was struck, or there's a private action underway, why isn't Adobe crying foul over this switcheroo, which is causing product confusion and support headaches?
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Is Google Poisoning PDF?

Comments Filter:

"I've seen the forgeries I've sent out." -- John F. Haugh II (jfh@rpp386.Dallas.TX.US), about forging net news articles