New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 7 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome downloads PDF instead of direclty opening it despite setting set correctly

Reported by orsch...@gmail.com, Jan 29 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Example URL:

Steps to reproduce the problem:
I made sure that "chrome://settings/content/pdfDocuments" is set to "Disabled" to download files. 

What is the expected behavior?

What went wrong?
But still, PDFs are downloaded and then once I click on them, opened in the browser. 

How can I directly open PDFs without having to download them?

Attaching a screencast to show you an example.

Thanks!

Did this work before? N/A 

Chrome version: 64.0.3282.119  Channel: stable
OS Version: Fedora 27
Flash Version: Shockwave Flash 28.0 r0
 
Screencast from 01-29-2018 11:27:03 AM.webm
929 KB View Download
Labels: Needs-Triage-M64
Cc: vamshi.k...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on rep[orted chrome version 64.0.3282.119 and on the latest dev 66.0.3334.0 using Ubuntu 14.04 with the below mentioned steps.
1. Launched chrome ()
2. In chrome://settings/content/pdfDocuments the option is disabled.
3. Navigated to a web page for few sample web pages.
4. Clicked on 2-3 links to view the pdfs
We observed that the PDFs opened in browser without being downloaded. Attaching the screen cast for reference.

@Reporter: Could you please check the screen cast and let us know if the issue is seen when trying to view any PDF or only specific PDFs. Any further inputs from your end helps us to triage the issue in a better way.

Thanks!  
806711.mp4
1.4 MB View Download
"Download PDF files instead of automatically opening them in Chrome" set to off/disabled works as suspected. The pdf loads in a new tab and is handled with Chrome's built-in PDF viewer.

"Download PDF files instead of automatically opening them in Chrome" set to on/enabled works as the description says. The pdf file is just downloaded.

However, Chrome and Opera users have mentioned a recent Chromium regression with the 2nd case (of on/enabled). The pdf is *just* downloaded and is no longer passed to the default pdf handler on the system. Users now have to click the download in the download dialog (click twice in Opera) to then have the pdf (well, the path to it) passed to the default pdf handler on the system. Users are saying it worked fine until recently where navigating to a pdf would automatically open it in the external handler.

I'm guessing the change was intentional, but if so, not sure why the change was needed in the first place and now users are unhappy.

Comment 4 by orsch...@gmail.com, Jan 31 2018

@vamshi.k...@techmahindra.com very helpful screencast!

Was able to reproduce but checkout mine. 

Why doesn't the PDF open in browser that I am trying to open from this Zendesk ticket?
Screencast from 01-31-2018 05:36:19 PM.webm
2.1 MB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 31 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by mmenke@chromium.org, Jan 31 2018

Components: -Internals>Network Internals>Plugins>PDF
Labels: Needs-Feedback
Tried checking the issue on reported chrome version 64.0.3282.119 using Ubuntu 14.04 with the steps mentioned below.
1. As per screen cast in comment#4, we have created a test account in "Zendesk ticket".
2. Tried logging in with the test credentials
3. Upon navigating to https://sheetgo.zendesk.com/agent/ticket to find a PDF we got a message saying "Access denied".
Attaching the screenshot of the same.

@Reporter: As we are unable to find any PDF to check, it would be highly helpful if provided with sample test credentials which helps us to triage the issue in a better way.

Thanks!
806711.png
100 KB View Download
@vamshi.k...@techmahindra.com let me try to get you a test account for Zendesk to reproduce!
Project Member

Comment 9 by sheriffbot@chromium.org, Feb 2

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: UI>Browser>Downloads
@vamshi.k...@techmahindra.com

Created this test environment for you.

You can log in with your email vamshi.k...@techmahindra.com.

https://d3v-chrome-debugging.zendesk.com/agent/tickets/2

Let me know!
Labels: M-66 FoundIn-66 Target-66 OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
@orschiro: Thanks for creating the test environment for my account, that was very helpful in triaging the issue further...!!

Able to reproduce the issue on reported chrome version 64.0.3282.119 and on the latest canary 66.0.3341.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is seen from M60(60.0.3072.0) considering it as Non-Regression and marking it as Untriaged. Hence requesting someone from Internals>Plugins>PDF or/and UI>Browser>Downloads team to look into this.

Thanks!
@vamshi glad to hear you could reproduce, thanks!
Owner: xingliu@chromium.org
Status: Assigned (was: Untriaged)
This setting maps to kPluginsAlwaysOpenPdfExternally in the code and only used by plugin system.

Download system uses other mechanisms. 
1. Plugin system seems can participate in some logic and tell download system it's safe to auto open. But might not respect this setting.
2. In download shelf context menu, there is an option to always open files based on extension. Seems download system respect this the most.

Safe browsing system also seems has control on if a file can be auto opened, probably security related.

Platform specific behaviors are built on the top of these.

I think the problem here is there are multiple mechanisms to determine if a file can be auto opened.


Cc: dtrainor@chromium.org
I believe this is not a download issue, that the setting is actually for web plugins that plugins can handle this instead of letting Chrome download system to handle this.

Only when this setting is disabled, it's download system's job to check if we should auto open, with chrome://settings -> Downloads. And users can click on download shelf context menu to specify if Chrome can auto open, and clear it in chrome://settings -> Downloads.
Cc: bauerb@chromium.org tommycli@chromium.org
Adds plugin owners for more thoughts on this bug.
Cc: vamshi.kommuri@chromium.org
 Issue 821921  has been merged into this issue.
Cc: sindhu.chelamcherla@chromium.org
 Issue 824973  has been merged into this issue.
Cc: susan.boorgula@chromium.org
 Issue 835271  has been merged into this issue.

Sign in to add a comment