New issue
Advanced search Search tips

Issue 660816 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Printing using system dialog does not handle non-square resolutions

Reported by stu...@testtrack4.com, Oct 31 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:
1. Have a printer with a mode for printing at a higher resolution in one dimension than the other; I'm using the Brother QL-700 Label Printer.
2. Print a page using the system dialog, using the printer options to select a resolution where the horizontal width is not the same as the vertical width (for instance, 300x600, on the QL-700).

What is the expected behavior?
The page should print at the correctly-transformed scale for the selected (and presumably reported) resolution, as it does when selecting the non-square resolution in Chrome's built-in, non-system print dialog (which is not necessarily an option: for instance, when I want to select a print length shorter than the default, I have to use the system dialog, as there's no way to select this from within Chrome).

What went wrong?
Chrome appears to send my printer a rasterization of the page at 300x300, which gets interpreted at 300x600 resolution and printed as a squished, half-height region in the middle of the "page".

Trying to work around this by applying a `body {transform: scaleY(2)}` style rule to the page does not work around the problem: though this transformation scales the printed area correctly, it still sends a rasterization at the dimensions that would be appropriate for the square resolution, meaning that only the center of the page is printed.

Did this work before? N/A 

Chrome version: 54.0.2840.71  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
 
Components: Internals>Printing
Does printing to the label printer work in IE/Edge/Firefox?

Maybe this snippet below is related. https://chromium.googlesource.com/chromium/src/+/master/printing/print_settings_initializer_win.cc#56 which was really written around 10 years ago, says: "No printer device is known to advertise different dpi in X and Y axis; even the fax device using the 200x100 dpi setting. It's ought to break so many applications that it's not even needed to care about. Blink doesn't support different dpi settings in X and Y axis."
Internet Explorer, after running Page Setup (without doing which, the print dialog *crashes the tab*), handles both 300x300 and 300x600 correctly, ie. no discernable difference between the two beyond print quality.

Edge's print dialog is too deficient to test this (no access to resolution adjustment nor the system print dialog).

Firefox exhibits a *completely different* buggy behavior at 300x600, where the full page is rendered at the correctly-transformed resolution, but text is rendered with double the appropriate inter-character spacing.

It's worth reiterating that Chrome handles 300x600 properly *as well*, when using its built-in print dialog - this issue manifests *only* when printing using the system dialog.
Labels: TE-Hardware-Dependency
How are you accessing the system print dialog? Are you using ctrl + shift + p directly, or clicking on "Print with system dialog..." from the print preview UI? Or do both of these methods have the same problem?
Labels: Needs-Feedback
Not sure if we are actually using the 300x600 dpi set in print preview; is this a cloud, extension, or privet printer?

The print preview dpi setting is ignored for everything other than cloud, privet, and extension printing. This is noted in  http://crbug.com/429393  where the setting was added and appears to still be true. For local printers, dpi is read from the printer in the print settings initializer, and we just take the x direction dpi. As noted in comment 1, in the initializer there is a comment stating that different x and y dpi values aren't supported.
Project Member

Comment 7 by sheriffbot@chromium.org, May 1 2017

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from reporter "stuart@testtrack4.com", so archiving this. Please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment