New issue
Advanced search Search tips

Issue 590787 link

Starred by 0 users
Status: Assigned
Owner:
thestig@chromium.org
Cc:
vitalyb...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Print data is 600dpi when 300dpi is expected

Project Member Reported by vitalyb...@chromium.org, Feb 29 2016 
The Local print dpi is set to 300dpi or 600dpi, and protocol parsing out dpi to 300dpi or 600dpi. But pwg headers are parsed out of 600 dpi and the actual data also is 600dpi.

Comment 1 by vitalyb...@chromium.org, Apr 4 2016

Owner: ----
Status: Available (was: Assigned)

Comment 2 by bblietz@chromium.org, May 23 2016

Owner: pwestbro@chromium.org
Project Member

Comment 3 by sheriffbot@chromium.org, May 24 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 4 by thestig@chromium.org, Apr 16 2018

Labels: -Pri-2 -Hotlist-Recharge-Cold Needs-Feedback Pri-3
Owner: thestig@chromium.org
Vitaly, do you remember more details about this bug?

Comment 5 by ellyjo...@chromium.org, May 21 2018

Cc: vitalyb...@chromium.org
Status: Assigned (was: Untriaged)
Mac triage: assigning to thestig@ for further triage.
►

Sign in to add a comment