Have you tried with other browsers besides Yandex? I tried some older version of Chrome and they also render to 2 pages. Firefox and Edge also do not fit the document to 1 page.

Yes, before we had no problems - the page was specially made for printing in chrome. And after the upgrade, all the people in the office could not print documents. When I began to deal with the problem, everything was fine with me, after I updated the browser the problem appeared and I have.
It's sad that even playing with css I could not fit the content onto one page.

Also everything is good in safari

Thank you for providing more feedback. Adding requester "thestig@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

Able to reproduce the issue on reported chrome version 64.0.3282.140 and latest canary 66.0.3346.0 using Mac 10.13.3, Windows-10 and Ubuntu 14.04 hence providing Bisect Info

Bisect Info:
================
Good build: 64.0.3260.0
Bad build: 64.0.3261.0

You are probably looking for a change made after 514198 (known good), but no later than 514199 (first known bad).

https://chromium.googlesource.com/chromium/src/+log/c52153c01b61f2ca8c78c86805cd7a493f456955..4c9edd832c4cf110cb73e2000f415da43a465681

Reviewed-on: https://chromium-review.googlesource.com/749949


@Nainar: Assigning to Nainar@chromium.org as robhogan@chromium.org last visit is 29days ago, please confirm the issue and help in re-assigning if it is not related to it.
Adding ReleaseBlock-Stable as it is seems a receent break, feel free to remove it if not applicable.

Thanks!

I suspect this is working as intended as the old behavior is considered incorrect but over to rob to verify.

Please forgive my inexperience with this tracker but I would not agree that this is working as intended.  With the recent updates to PC Chrome version 64.0.3282.167 the printing to PDF has radically changed its rendering.  We use Chrome to produce PDF proposals and have a page that was specifically designed/styled for Chrome Print to PDF.  We have been using it for years but after the recent update the page still looks and functions the same while in the browser but when you go to print the preview and resulting PDF look complete messed up.

If there is any information I can provide to be of assistance I would gladly do so.  Thank you for your consideration.

Attached to this comment are two PDFs that were printed using Chrome's Print to PDF.  They are created using the exact same page.  The working one was printed prior to version 64.0.3282.167 and the broken one was done using version 64.0.3282.167.

Deleted: proposal_working.pdf 4.7 MB

proposal_working.pdf 4.7 MB Download

Deleted: proposal_broken.pdf 4.6 MB

proposal_broken.pdf 4.6 MB Download

I am experiencing similar issues with print layout and scaling. Have been printing PDFs from Chrome for the months and now they look like the broken pdf. Can anyone provide context and info on what actually caused this change?

Deleted: PDF-Working.pdf 470 KB

PDF-Working.pdf 470 KB Download

Deleted: PDF-Broken.pdf 354 KB

PDF-Broken.pdf 354 KB Download

Adam,  Your PDFs are a perfect example of what I'm experiencing.  I'm shocked that this issue hasn't received more attention.  Is this a duplicate of another issue that we should be starring or commenting on?

Comments 9 and 10 - can you provide a sample HTML page that demonstrates the issue in case you are seeing a different problem? The reason that comment 7 suggests this might be working as intended is:
(1) The change that caused this reverts to the behavior in Chrome 53 and earlier. I tested the webpage in the original report in Chrome 53, 63, and 64 and it prints the same way in 53 and 64, and differently in 63.
(2) The behavior in 63 is a bit odd, because the print layout depends on the size of the browser window. When I tested the sample page on Chrome 63, the document fit on one page if the browser window is large enough, but needed 2 pages if the browser window was smaller. In 53 and 64 the page is laid out the same way for printing regardless of the size of the browser window. The fact that print layout was changing based on the size of the window led to bug reports, which is why the change was made.

Unfortunately, it seems this sample page relied on Chrome using the browser window size for print layout (and on the browser window being > 1200px). Specifically, see the following CSS, which sets the width based on the media size. If the container element is set to always have width: 1170px it prints one 1 page in 64.

@media (min-width: 1200px)
.container {
    width: 1170px;
}
@media (min-width: 992px)
.container {
    width: 970px;
}

@media (min-width: 768px)
.container {
    width: 750px;
}

To test the PDF generation mentioned in comment #9 you can use this URL

https://www.intulse.com/sign-up/proposal?pid=SKQI9LQ5

Please note, you will need to wait for it to finish loading THEN click on the "Review & Approve" tab.  Then you can you either click the "View" button or just CTRL+P.

Also... When you have the print dialog open you should set the page margins to none, that's how it was designed to work.

Morten, would you mind taking a look at this while Rob is out?

I tried the URL in comment #13, after reverting the blamed CL (comment #6), and sure enough, things look nice again.

But ONLY if the browser window is wide enough:
Maximized (1920px wide on my screen) it looks nice. At 1600px too. Even at 1200px. And at 1000px. But at e.g. 960px it acts up, and it ends up looking like proposal_broken.pdf .

The bug in Chrome, prior to the blamed CL, was that the size of the browser window affected print layout, which is just wrong. That was a bug that existed in Chrome between August 2016 and November 2017.

I guess I'm just repeating and confirming what others have posted before me here, but it's the sites that need to be fixed. Width media queries will now be matched against the output device (and the window size on the screen should really not be involved when the output device is the printer). This is according to the spec, and the only browser known to have violated it, is Chrome between version 54 and 63.

There are more than one site mentioned in this bug report. As far as the original site is concerned, comment #2 seems to support the theory that, in order to trigger the desired zooming, the sites depended on this bug that existed in Chrome for a bit over a year.

Thanks for the detailed explanation Morten.