Hey Tommy,

What's the expected behavior for this case?

Hey,

This seems to be a bad case where Chrome is also the default system viewer for PDF.

On my particular (Linux) machine, when you click "View PDF", it opens the Adobe Reader equivalent for Linux.

I'm not sure what the right thing to do when there is no PDF viewer installed other than Chrome. Probably show a dialog saying: "No PDF viewer installed"...

I will have to investigate further.

TE: Can you still reproduce this if you install a different PDF viewer? i.e. Adobe Reader.

@tommycli: Just to update, Able to view the PDF using Adobe Reader.

Thanks!!

There isn't anything confidential on this issue, removing the restriction.

sandeepkumars: I have one more test for you to run.

1. Uninstall Adobe Reader, and and verify that you can still reproduce the issue in the screencast.

2. Now disable chrome://flags/#click-to-open-pdf, but keep chrome://settings/content/pdfDocuments enabled.

3. Goto http://chrome-pdf-test.appspot.com and click #1. What happens when you click the downloaded PDF? Is it the same behavior?

I'm trying to figure out if this issue is caused by this feature, or if it's a "pre-existing condition".

I tested this myself, and it's a pre-existing condition predating click-to-open-pdf.

Here's the repro steps (assuming Chrome is also the system PDF viewer):

0. Uninstall all other PDF viewers (make sure Chrome is the system PDF viewer).

1. Goto chrome://settings/content/pdfDocuments and enable "Download PDF files instead of automatically opening them in Chrome"

2. Goto http://chrome-pdf-test.appspot.com and click Case #1, Direct link to PDF.

3. Observe that the PDF is downloaded.

4. Click on the downloaded PDF.

5. Observe that Chrome is the system default PDF viewer... but it just re-downloads the exact same file.

It's unfortunate, and we should fix it -- probably with a modal dialog explaining what's going on. It's existed "forever" though, so it's not time critical.