PDFs can no longer just be saved when built in PDF viewer is disabled
Reported by
turbo2...@gmail.com,
Jan 11 2017
|
|||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Go into settings-> content settings -> PDF Documents and turn on "Open PDFs using a different application" 2. Click on a link to a PDF in a web page 3. What is the expected behavior? The file downloads and shows up in the pop up download bar at the bottom of the window. At that point you can drag it to an email or click on it to open. What went wrong? It downloads and opens automatically in the system viewer whether you want to open it or not. Even if you right click link and click "Download link", it still automatically opens even if you don't want it to. Did this work before? Yes November-ish I believe it still worked. Chrome version: 57.0.2978.0 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0 I posted on the google help forum on 12/2 with no useful replies. https://productforums.google.com/forum/#!topic/chrome/8EgIOSS6SPQ
,
Jan 12 2017
Able to reproduce this issue on Windows-7 &10, Ubuntu 14.04 and Mac OS 10.12 using chrome latest canary M57-57.0.2978.0 by following steps mentioned in the original comment. Observed the PDF file disappears immediately from download tray and it opens automatically. Reporter@ - Could you please confirm is this is the issue you are talking about it? If yes, I am able to reproduce this issue on M56 as well. Do you have any idea that on which version it used to work before? Thanks!
,
Jan 12 2017
That is indeed the issue. PDFs do not behave like other file types. Looking at the log, this is the install progression (newest first): 57.0.2978.0 1/11 57.0.2977.0 1/10 57.0.2971.0 1/4 57.0.2928.0 11/23 56.0.2922.0 11/17 The log on 11/7 says it deleted stray directory 55.0.2869.0 11/17 lines up with when I remember noticing it. Prior to 11/17 the log messages seem to change and I'm not seeing the same log entries for installs, just what seem to be error messages dating back to 2015 with entries like this in repeating blocks: [0826/042033:ERROR:install_worker.cc(209)] Failed creating a firewall rules. Continuing with install. [0826/042034:ERROR:create_reg_key_work_item.cc(85)] Failed to create Software\Microsoft\MediaPlayer [0826/042034:ERROR:install.cc(141)] Could not add Chrome to media player inclusion list. [0826/042034:ERROR:installer_state.cc(567)] Deleting old version directory: C:\Users\mike\AppData\Local\Google\Chrome SxS\Application\54.0.2839.2 [0826/042035:ERROR:installation_validator.cc(289)] Chrome Binaries are present yet Chrome is not multi-install. [0826/042035:ERROR:setup_main.cc(1869)] [0826/074630:ERROR:delete_after_reboot_helper.cc(73)] Could not schedule C:\Users\mike\AppData\Local\Google\Chrome SxS\Temp\scoped_dir_6164_21068\old_chrome.exe for deletion.: Access is denied. (0x5) [0826/074630:ERROR:delete_after_reboot_helper.cc(129)] Failed to schedule file for deletion: C:\Users\mike\AppData\Local\Google\Chrome SxS\Temp\scoped_dir_6164_21068\old_chrome.exe [0826/074630:ERROR:delete_after_reboot_helper.cc(144)] Failed to schedule subdirectory for deletion: C:\Users\mike\AppData\Local\Google\Chrome SxS\Temp\scoped_dir_6164_21068 [0826/192013:ERROR:install_worker.cc(209)] Failed creating a firewall rules. Continuing with install. [0826/192014:ERROR:create_reg_key_work_item.cc(85)] Failed to create Software\Microsoft\MediaPlayer [0826/192014:ERROR:install.cc(141)] Could not add Chrome to media player inclusion list. [0826/192014:ERROR:installer_state.cc(567)] Deleting old version directory: C:\Users\mike\AppData\Local\Google\Chrome SxS\Application\54.0.2837.0 [0826/192015:ERROR:installation_validator.cc(289)] Chrome Binaries are present yet Chrome is not multi-install. Seems unrelated. Hope this helps.
,
Jan 12 2017
* The log on 11/17 says it deleted stray directory 55.0.2869.0
,
Jan 14 2017
,
Jan 16 2017
Possible place of introduction. https://chromium.googlesource.com/chromium/src/+/8c7be7eaa985a8b4a29de3dda25963f4f2f12c86
,
Jan 17 2017
As per comment #6 assigning to the concerned person for more updates on this issue pastarmovj@ Do you have any update on this issue?
,
Jan 17 2017
This sounds like a side effect of the way we handle PDFs in the post about://plugins world indeed. I will investigate asap. Adding asanka fyi.
,
Jan 20 2017
,
Feb 2 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7c93dbe0d5fe53372321fa53368377ee6770405a commit 7c93dbe0d5fe53372321fa53368377ee6770405a Author: pastarmovj <pastarmovj@chromium.org> Date: Thu Feb 02 16:14:34 2017 Revert changes to download_prefs regarding PDF auto open. In https://codereview.chromium.org/2369353002/ we introduced logic to automatically open the program associated with PDF when the always open PDF in external viewer was selected. This causes some issues where saving of PDFs becomes harder or cumbersome. Until we figre better way to decided when to auto-open and when not revert this logic. BUG= 680202 TEST=This is revert to existing state covered by existing tests. Review-Url: https://codereview.chromium.org/2669773002 Cr-Commit-Position: refs/heads/master@{#447773} [modify] https://crrev.com/7c93dbe0d5fe53372321fa53368377ee6770405a/chrome/browser/download/download_prefs.cc [modify] https://crrev.com/7c93dbe0d5fe53372321fa53368377ee6770405a/chrome/browser/download/download_prefs.h [modify] https://crrev.com/7c93dbe0d5fe53372321fa53368377ee6770405a/chrome/browser/download/download_prefs_unittest.cc
,
Feb 3 2017
Issue 688434 has been merged into this issue.
,
Feb 6 2017
Requesting merge permissions for https://codereview.chromium.org/2669773002. I think it will be better if we reverted to the safer behavior as soon as possible.
,
Feb 6 2017
This bug requires manual review: Reverts referenced in bugdroid comments after merge request. Please contact the milestone owner if you have questions. Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 6 2017
Approving merge of revert to M57 branch 2987 based on comment #12. Pls merge ASAP. Thank you.
,
Feb 6 2017
Please merge your change to M57 branch 2987 before 5:00 PM PT, Tuesday (02/07/17) so we can pick it up for next Beta release. Thank you.
,
Feb 6 2017
,
Feb 7 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/58f25776d2ee7cacc0a3d0a6a9be90184d944adf commit 58f25776d2ee7cacc0a3d0a6a9be90184d944adf Author: Julian Pastarmov <pastarmovj@chromium.org> Date: Tue Feb 07 07:37:59 2017 Revert changes to download_prefs regarding PDF auto open. In https://codereview.chromium.org/2369353002/ we introduced logic to automatically open the program associated with PDF when the always open PDF in external viewer was selected. This causes some issues where saving of PDFs becomes harder or cumbersome. Until we figre better way to decided when to auto-open and when not revert this logic. BUG= 680202 TEST=This is revert to existing state covered by existing tests. Review-Url: https://codereview.chromium.org/2669773002 Cr-Commit-Position: refs/heads/master@{#447773} (cherry picked from commit 7c93dbe0d5fe53372321fa53368377ee6770405a) Review-Url: https://codereview.chromium.org/2683543002 . Cr-Commit-Position: refs/branch-heads/2987@{#356} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} [modify] https://crrev.com/58f25776d2ee7cacc0a3d0a6a9be90184d944adf/chrome/browser/download/download_prefs.cc [modify] https://crrev.com/58f25776d2ee7cacc0a3d0a6a9be90184d944adf/chrome/browser/download/download_prefs.h [modify] https://crrev.com/58f25776d2ee7cacc0a3d0a6a9be90184d944adf/chrome/browser/download/download_prefs_unittest.cc
,
Feb 7 2017
The fix has been merged in 57 and will be available in the next beta release.
,
Feb 14 2017
,
Feb 21 2017
,
Mar 9 2017
Was directed to this thread by one of the Community Specialists in the Google Chrome Help Forum where I posted an issue that seems to be similar. PDF files downloaded from the web are opening automatically. Previously - perhaps up until a month or so ago - when I downloaded a PDF in Chrome, I would see my downloads in a download tile bar at the bottom of my screen and I could then click on it to open after downloading. No change has been made to my PDF reader (Foxit). And other than an update to either Chrome or Foxit, I have not made any changes to either program. I also cannot find in either application, a setting that keeps them from doing so. Although there is something in Chrome/Settings/Downloads/ there is a note that says: "You have chosen to open certain file types automatically after downloading." Actually, I haven't - this would have been the default settting whenever I installed Chrome 3-1/2 years ago on this computer as I've never asked anything to open automatically. There is also a button below that note that says "Clear Auto-Opening Settings" which I click on, but nothing opens, pops up and in general this button doesn't seem to do anything. PDFs still open automatically. I have been able to replicate this issue on a different computer with the same versions of Windows and Chrome.
,
Mar 11 2017
R 57.0 is now available. I have installed and am in the process of verifying that this annoying issue is hopefully fixed!
,
Mar 17 2017
Still same issues in R57.0
,
Mar 17 2017
I just tested 57.0.2987.110 on Linux which was just rolled in, and it appears fixed here.
,
Mar 19 2017
Just updated to Version 57.0.2987.110 (64-bit) and PDFs are being viewed within Chrome with chrome viewer (I have Open PDF Files In Default PDF Viewer Application UNchecked and always have) but once downloaded to my computer, my system PDF viewer (Foxit Reader) opens up automatically with the PDF in it. This was not happening a week ago. Windows 10 (recent update was Tuesday 3/14)
,
Mar 28 2017
It seems the auto open setting have been flipped for for pdf (could be a fallout from flipping the open pdf externally open, which is being investigated now). You can go into the Settings page of Chrome and clear the auto-open list by opening the Advanced settings link at the bottom, scrolling down to the "Downloads" section and using the button to clear the auto open settings. This will reset the downloads to not open automatically for you.
,
Mar 28 2017
Is there a bug report for follow for "flipping the open pdf externally open, which is being investigated now" ?
,
Mar 28 2017
I created https://bugs.chromium.org/p/chromium/issues/detail?id=705979 to track this work.
,
Apr 10 2017
I can confirm this is still an issue. Just did the following for a user: Had issues with English PDF document language displaying in Greek, when viewed with Chrome 54 PDF viewer. 1. User was on Chrome 54 2. Disabled Chrome PDF Viewer via the chrome://plugins page 3. Tested same link to the document and it came up fine in Adobe Reader after the file was saved to local machine 4. Checked same document link on my system, Chrome PDF viewer worked fine, document was in English 5. Checked my version, which was 57 6. Uninstalled Chrome 54 from user's machine 7. Reinstalled new Chrome 57 from Google's website 8. Used document link and it still downloaded the document and it did not come up on Chrome Viewer 9. Went to Content Settings and unchecked "Open PDF Files in the default PDF viewer application" 10. Closed Chrome and reopened it 11. Went to same document link, link STILL downloaded and didn't open in Chrome Viewer 12. Validated Content Settings and option appears to have rechecked itself 13. Unchecked setting again and closed Chrome 14. Open Chrome and looked at the Content Setting again 15. Rechecked itself. WILL NOT UNCHECK. Whatever the previous Chrome version's setting was for the Chrome PDF Viewer, becomes a permanent setting in the newly installed Chrome 57.
,
Apr 11 2017
Could it be that on this other machine the setting is controlled by enterprise policy? Can you check if anything shows up when you open chrome://policy ?
,
Apr 11 2017
None set and others can use Chrome PDF Viewer just fine. Gut says it's an issue with disabling the chrome pdf viewer in a previous version and upgrading to 57... Also, for an additional detail, on uninstall of 54 I did not remove personalized settings/history. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by turbo2...@gmail.com
, Jan 11 2017