New issue
Advanced search Search tips

Issue 713672 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Compat



Sign in to add a comment

Chrome PDF Viewer displays and prints images within PDF with black artifacts

Reported by d...@9summer.com, Apr 20 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0

Example URL:

Steps to reproduce the problem:
 * Open the attached PDF in Chrome on Windows 10 (other users have reported it's reproducible on at least Mac, maybe Linux too)
 * Click File -> Print
 * Note that the QR Codes have black lines through them
 * Print the file

What is the expected behavior?
The QR code should not have black lines through it on the screen nor the printed output

What went wrong?
The QR code has black lines through it on the screen and depending on the number of pages and number of images in the PDF (this repro case is not as consistent), the printed output also has black lines

Does it occur on multiple sites: N/A

Is it a problem with a plugin? Yes Chrome PDF Viewer

Did this work before? Yes Prior to at least March 14 it was working properly; that was the first report of this problem from our customers

Does this work in other browsers? Yes

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 10.0
Flash Version: 

This is almost identical to  Issue #710882  and commentary has already happened on that ticket. I was asked to open this ticket since the original ticket description varied enough that weili asked me to open this separate ticket
 
POSTickets.pdf
77.7 KB Download
2017-04-18_1612.png
150 KB View Download

Comment 1 by weili@chromium.org, Apr 20 2017

Labels: Needs-Feedback
hi, dave@, thanks for filling the bug.

I checked it on different platforms and versions. Looks like it is a regression that is fixed on v58. Could you pls update your chrome to version 58 and check?

Comment 2 by d...@9summer.com, Apr 20 2017

Awesome, yes, initial testing on v58 confirms the problem is gone.

I have to have a few testers confirm but we can assume this is resolved 
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 20 2017

Cc: weili@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "weili@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 4 by weili@chromium.org, Apr 20 2017

Status: Fixed (was: Unconfirmed)
thanks for the quick response!

Sign in to add a comment