Issue metadata
Sign in to add a comment
|
PDF files displaying blank pages (Chrome PDF viewer)
Reported by
to...@utcourts.gov,
Apr 12 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Example URL: Internal systems - Utah Courts Steps to reproduce the problem: 1. Accessed 2 different internal systems 2. Opened PDF - multiple pages and it displays a page count but all pages are blank 3. Works in IE, Edge, FireFox and Safari without issue. 4. PDF can be downloaded and forced to open in Adobe Reader without issue What is the expected behavior? To display the contents of the document What went wrong? Document display is blank beyond page count Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? Yes Version 48 Does this work in other browsers? Yes Chrome version: 49.0.2623.110 Channel: n/a OS Version: 7 & 10 Flash Version: Shockwave Flash 21.0 r0 We had this same problem when version 46 came out. It was fixed with 47 and worked through 48. Broke again with 49
,
Apr 13 2016
Can you attach a PDF which reproduces the issue? With an example file it's hard to debug what's going on.
,
Apr 13 2016
Attached are two sample files: OriginalPDF.pdf is the original file, and FailedPDF.pdf is the digitally signed file of the original PDF. We can view OriginalPDF.pdf without any problem in Chrome, however when it is digitally signed, FailedPDF.pdf shows blank in Chrome. This problem appeared only after we upgraded Chrome to version 49.
,
Apr 15 2016
Indeed it used to work for a bit and is now broken. Tracking it down...
,
Apr 15 2016
Regressed with https://codereview.chromium.org/1527823003 Bug reporters: If it is important that these PDFs work for you, please consider installing and occasionally using Google Chrome Canary, so you can report these issues earlier.
,
Apr 18 2016
,
Apr 26 2016
DEPS rolled today.
,
Jun 6 2016
What version of Chrome will have this fix?
,
Jun 28 2016
The status on this is still listed as "Fixed". I have updated to Version 51.0.2704.106m this morning and the issue still exists. Is there an ETA on when this will be moved into the production browser?
,
Jun 28 2016
52.0.2717.0 and newer has the fix. As of this writing, Chrome beta/dev/canary channel, but not stable. Let's see if we can merge the fix to Chrome 51.
,
Jun 29 2016
[Automated comment] Request affecting a post-stable build (M51), manual review required.
,
Jun 29 2016
Before we approve merge to M51, Could you please confirm whether this change is baked/verified in Canary and safe to merge?
,
Jun 29 2016
It's been on non-stable channels for 2 months now. Safe AFAIK. https://codereview.chromium.org/1910063004 is the fix. Not sure why bugdroid didn't chime in on the bug here. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by b...@chromium.org
, Apr 12 2016