Slashdot Mirror


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."

3 of 202 comments (clear)

  1. Great by sexconker · · Score: 5, Insightful

    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.

    1. Re:Great by LunaticTippy · · Score: 5, Insightful

      I understand hating the built in viewers, but to me they are a blessing. There are so many things that are PDFs for no reason. I really appreciate a quick and dirty way to see PDFs, and with my usage it is good enough 90% of the time. For the interactive ones etc. I tend to recognize which ones aren't going to work so I just download the file. On unfamiliar systems I always grit my teeth when clicking a link causes a 20 second delay while Adobe Viewer lurches from the shadows and demands to be updated.

      --
      Man, you really need that seminar!
    2. Re:Great by Anonymous Coward · · Score: 5, Insightful

      If a new feature is added by way of an update, it should prompt for its settings the first time it becomes relevant. So on the first click on a PDF the browser should prompt: "you can now view PDFs within the browser, enable / disbale this feature / let me try once and prompt me again." It shouldn't silently enable the feature and let the hapless user hunt in the settings for a way to disable it, that's just rude.