Please provide a sample PDF file that shows this problem.

The pdf as shown on my computer shows up fine on the screen, and also prints cotrectly when printed by my windows computer. But as you can see in the other picture, when I print using my chromebook the font spacing is incorrect. When I click "inspect" in the pdf, I get the warning error as shown in the last picture that says the html imports are deprecated.

Is there any wat to fix this? I need to print a lot of documents with the html imports. Thank you. 

Deleted: 20180222_094051.jpg 1.6 MB

	20180222_094051.jpg 1.6 MB View Download

Deleted: 20180223_093243.jpg 1.7 MB

	20180223_093243.jpg 1.7 MB View Download

Deleted: 20180223_093710.jpg 1.6 MB

	20180223_093710.jpg 1.6 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

Can you provide the pdf file (or any pdf file that illustrates the problem)?  That would probably be much more helpful than pictures of the incorrect output.

Can you upgrade to 64.0.3282.186 and see if the problem has gone away? You can check the version and update status by navigating to: chrome://settings/help

Just to clarify: Are you sharing the printer as a cloud printer from your Windows computer to your Chromebook? Please try to upgrade both computers. The Windows computer may need a reboot after upgrading.

I'm printing from my Chromebook through google print to my printer that's on my wifi network. I only used the Microsoft computer to see if it prints fine and it does so I know the issue is with my Chromebook.

I upgraded to 64.0.3282.186 and it didn't fix the problem. I attached a file that has the same problem. 

Deleted: test quote.pdf 2.3 KB

test quote.pdf 2.3 KB Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

Attached is the scanned output.

Deleted: 20180305094340.pdf 372 KB

20180305094340.pdf 372 KB Download

I tried with a Chromebook here. I printed "test quote.pdf" via Cloud Print to a nearby printer and it came out fine. Since I can't (easily) reproduce the bug, I have some responses to previous comments and more questions:

re: comment 3 - The "html imports are deprecated" message is a red herring.
re: comment 10 - When you say "google print" - did you mean "Google Cloud Print" ? If this is Google Cloud Print, you should be able to see the print jobs listed on https://www.google.com/cloudprint/#jobs

If yes, is your printer registered with Google Cloud Print directly? i.e. If you turn off your Windows computer, can you still print from the Chromebook? I just want to make sure the Windows computer is not acting as a bridge to the printer.

Did this work previously? e.g. A few weeks ago, presumably with Chrome 63 on the same Chromebook and the same printer.

What's the make and model is the printer?

And here's a possible workaround: Is there a "Print as image" checkbox in Print Preview? Can you try using that and see if that improves the situation?

"2. re: comment 10 - When you say "google print" - did you mean "Google Cloud Print" ? If this is Google Cloud Print, you should be able to see the print jobs listed on https://www.google.com/cloudprint/#jobs"  
     - When I click this they don't show so I'm not sure.  I also attached a screen shot of my devices that show it's a cloud printer. 

Printer Type
Cloud Ready Printer
Registered with Cloud Print
Feb 21, 2018, 5:56:51 PM
Last Updated
Mar 7, 2018, 1:26:53 PM
Manufacturer
Canon.Inc
Model
MF620C Series
Google Cloud Print Version
2.0
Firmware Version
03.01
Firmware Update URL
http://www.canon.com/support/
Supported Content Types
image/pwg-raster
Proxy
canon.gcp.TSG13558


"3. If yes, is your printer registered with Google Cloud Print directly? i.e. If you turn off your Windows computer, can you still print from the Chromebook? I just want to make sure the Windows computer is not acting as a bridge to the printer."
       Yes, if the windows computer is off, it still works.


"4. Did this work previously? e.g. A few weeks ago, presumably with Chrome 63 on the same Chromebook and the same printer."  
        Yes it did and the problem didn't start happening until right before I filed this bug report. 


"5. What's the make and model of the printer?"
        This shows MF620C Series but on the front of the printer it says mf628cw.

And he is suggesting the possible workaround: Is there a "Print as image" checkbox in Print Preview? Can you try using that and see if that improves the situation? 
      No, I tried this a few times and it's still the same. 

Deleted: Screenshot 2018-03-07 at 3.57.07 PM (1).png 124 KB

	Screenshot 2018-03-07 at 3.57.07 PM (1).png 124 KB View Download

Angela: Thanks for the clarifications. I just want to confirm one more thing: Is the print preview rendered correctly?

Paolo: Assuming I read comment 15 correctly, when a Cloud Printer only supports the PWG raster format, who does the PDF to PWG conversion? Is it

a) Client - Chrome uploads PWG data to server; server sends PWG data to printer

or

b) Server - Chrome uploads PDF data to server; server sends PWG data to printer

Yes it shows up correctly in the print preview.

I think the reason I can't reproduce this bug is because my cloud printer accepts PDFs. I suspect the answer to the question in comment 16 is (b), so this may be a Cloud Print server-side bug.

Okay that sounds right.

I'd like to understand the reason why the job is not listed on https://www.google.com/cloudprint/#jobs . A timeout occurs while getting the list of jobs, or the job just doesn't show up on the list?

In the latter case it is very likely that the job is sent directly - over local network - to the printer without passing through the server. In that case the PWG-raster generation happens in chrome.

The answer for the question in comment 16 is indeed (b).

Paolo: Oh, if it is not being sent to the Cloud Print server, then this may be Privet printing on the local network. In which case, yes, I think the Chromebook itself is doing the PDF to PWG conversion. I'll try to check that case.

Angela: Can you see if your Chromebook has updated to 64.0.3282.190? One PDF bug that I am aware of is  bug 814883 , and that recently got fixed.

As an additional note, I've tried passing the provided document to the server-side conversion engine, and the generated PWG-raster document didn't show the font problems as I can see in the attachment of comment #12.

Paolo: Thanks for checking. I'll take this bug back then.

Happy April. Just wanted to check in again to see if the printing issues resolved themselves with ChromeOS updates.

Haven't heard back in a few weeks. I'm going to hope for the best and assume this issue has gone away. Please let us know if that is indeed the case.

Hi,

I'm still having problems with this.

What version has the Chromebook updated to? You can check via:
- The 3 vertical dots menu -> Help -> About ChromeOS

Got another customer with similar issue. PDF - 
https://drive.google.com/file/d/1v2UK1c4zZQztDh33vT_vI8zWFYRY-imk/view?usp=sharing

I was able to repro on my corp Linux with balmy-color printer. 
Print result - 
https://drive.google.com/file/d/1n71JiyEaZD-eZs-z6mCPpnRP7dEP-34T/view?usp=sharing

Prints fine as image. 

Not sure if the same issue, as it reproduces on Windows and Linux, but printing result looks the same.

re: comment 28 - Can you file a separate bug for your issue? It may be diffent, though the symptoms are similar.

Re: #29 Filed new  crbug.com/845697  and did bisect there.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.