New issue
Advanced search Search tips

Issue 861760 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 10
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

PDFs not loading, get blank/black screen

Reported by nlbar...@gmail.com, Jul 9

Issue description

Chrome Version       :  52.0.2743.82 (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK 11.1.1 (12605.2.8)
    Firefox: OK 61.0.1 (64-bit)
       Edge:

What steps will reproduce the problem?
(1) at any web site, click on a PDF link
(2) Chrome switches to new tab but screen is black. PDF is not displayed.
(3) tried the various remedies in the 2017  bug 697574  and Chrome help thread, unsuccessful

What is the expected result?

PDF should open in new tab.

What happens instead?

Switches to new tab but window is black. PDF content cannot be seen.

Please provide any additional information below. Attach a screenshot if
possible.

 
Screen Shot 2018-07-09 at 11.15.36 AM.png
90.4 KB View Download
Chrome 52 is no longer supported.
Try updating to the current version which is 67.
Labels: Needs-Milestone
Components: Internals>Plugins>PDF
Labels: Needs-Feedback
OK, updating to v 67 seems to have fixed it.  In my defense, I did check About Chrome when the problem occurred, and it assured me that "Google Chrome is up to date" at v 52.  See attached screenshot. Hope that one is fixed as well....
Thanks!
Screen Shot 2018-07-09 at 9.39.11 PM.png
44.8 KB View Download
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 10

Cc: hnakashima@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -hnakashima@chromium.org
Owner: hnakashima@chromium.org
Status: WontFix (was: Unconfirmed)
Thank you for verifying.

If you're willing, please file a bug to the component Internals > Installer about the update issue.

Sign in to add a comment