Problem printing multi-page documents from Chrome

[Richard]

A customer reported and I have reproduced a problem when printing from Chrome. If you open a document in chrome for viewing (pdf attached to an email or pdf stored in drive) and then print it by using ctrl-P or any of the print buttons, displaying the basic chrome print dialog, select all pages and a GCP printer selected with the destination change button  (not using the Print with Google Cloud Print option), the CJT that is downloaded to my proxy app for that job contains this: "page_range":{"interval":[{"start":1,"end":1} which indicates a user selected page range of just the first page. My proxy code obeys this and prints only the first page.

If, on the chrome print dialog, you select Print with Google Cloud Print and then select the printer from the GCP dialog that opens, the page_range item is not in the CJT (as you would expect if you select all pages) and the document prints correctly with all pages.

[rickardlu...@gmail.com]

I have the exact same problem! 

We are running Cloud Print Service on a Windows 2012 Server. And i can't find a solution to the problem.

[Richard]

I have reconfirmed this problem today. This seems a serious bug in the Chrome print dialog that would be causing failure of any printing done from the Chrome print dialog to any device or proxy using the CJT and obeying the page_range item.

[Rickard Lundqvist]

We got it to work! It was a bug in the software. (Cloud Print for Windows). If you are using that software to run the service on the server, update to 1.6.32 to fix the issue. 

[Richard]

Actually it should be v1.6.33 (available yesterday) as there was an additional issue related to this problem.

[Richard]

To the GCP team. We had an extensive offline discussion about the page range issues a couple weeks ago. At that time I was told that when printing from the Chrome print dialog, if you select all pages, the default page range set by the printer CDD would be sent in the ticket. This caused me a problem because I was setting the default page range incorrectly in my CDD, so I corrected my default to be open-ended per the CDD documentation.

Now today I observe that an incorrect CDD default of start=1,end=1 is not being downloaded by Chrome dialog when All pages is selected. In this case  the ticket contains and empty page range. Has Chrome been changed to force the empty range when all is selected? If so what version of Chrome was this changed it?

[Robert Toscano]

Hi Richard, would it be possible to send us the CDD (just the page range part would be fine), the ticket that you downloaded, and tell us if the downloaded document had pages removed from it?

--
You received this message because you are subscribed to the Google Groups "Google Cloud Print Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gcp-developer...@googlegroups.com.
Visit this group at http://groups.google.com/group/gcp-developers.

To view this discussion on the web visit https://groups.google.com/d/msgid/gcp-developers/b5ee84eb-d34f-4c58-b673-ac3b301707ae%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Richard Corn]

Robert,

Here is what is happening:

 

Unfortunately my code was still sending CDD with page_range start=1;end=1 which I discovered yesterday after a customer notified me of one page printing. What happens when a document is uploaded to GCP via the API, and no page range is set in the CJT, the server uses the default and in this case, strips out all but the first page to create the download file and sends empty page_range in the downloaded CJT. This is what I was told earlier would be the behavior and I needed to send a default page_range of start=1;end=nothing (don't send) which is open-ended range. When I do this, the server does not apply any page range as expected but does send empty page_range in the downloaded CJT.

 

Just a lot of confusion about the page_range rules, who is supposed to implement page_range and then an error on my part.

 

Sending a "default" page_range in the CDD does not seem to make sense as discussed earlier but I am still sending it as I have the understanding that you need to send page_range in CDD in order to have page range selection displayed on the GCP web page for the printer. Empty page_range in the downloaded CJT seems pointless...unless there is a case where the server will actually send page_range(s) to the printer?

Richard Corn
Software Devices LLC / RAC Consulting / PTP Security
P.O. Box 12299
Olympia, WA. 98508
360.357.9572   fax 360.352.8453
r...@swdevs.com     www.swdevs.com    www.ptpsecurity.com

You received this message because you are subscribed to a topic in the Google Groups "Google Cloud Print Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gcp-developers/sdHNumS_k1U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gcp-developer...@googlegroups.com.

Visit this group at http://groups.google.com/group/gcp-developers.

To view this discussion on the web visit https://groups.google.com/d/msgid/gcp-developers/CAJUBiFi9NO%3DgWFibY3a%2BCd-FL0d-Z%3Dix7paMvZqwTB-FOqKrQQ%40mail.gmail.com.

[Paolo Ferraris]

Hi Richard,

sorry for the delay. I think that I've identified the issue. We'll work on a fix very soon.

To view this discussion on the web visit https://groups.google.com/d/msgid/gcp-developers/004701cf5e49%248f82a0c0%24210cd0a1%40DEXLAB.RACC.COM.

[Richard Corn]

I'm curious what you will be fixing. I think the problem is that I was sending the default page_range incorrectly and that did not cause a problem until you changed the server to use the default when no page_range is sent, which is what I was told earlier would happen and is acceptable...I just failed to get my code corrected. So from my point of view, this not a problem per se.

 

I would argue for clarification of the role of the page_range in the CDD and CJT to make sure we are all on the same page, so to speak.

To view this discussion on the web visit https://groups.google.com/d/msgid/gcp-developers/CALXQsg-59H%2B8Am62nvVYq6www6TJyZFwi_x9bmR8gqBB1D-uzA%40mail.gmail.com.

[Paolo Ferraris]

Richard,

we decided to ignore the value for page range in printer's cdd, and default it to all pages. We can't expect every single client to support page range properly and we believe that any other default value than all pages would be undesired by the user. A default value for page range should be managed more at the level of client/cloud, and not set on the actual hardware.

We will update the documentation accordingly.

We are also planning a client API change that will separate more the concepts of a printer CDD vs. print dialog CDD (containing cloud-managed options). More details will come out in a few weeks. Stay tuned.

To view this discussion on the web visit https://groups.google.com/d/msgid/gcp-developers/003f01cf5f5e%24bedf8d40%24210cd0a1%40DEXLAB.RACC.COM.