Google Docs never prints in landscape when using GCP on OSX browser host |
||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: OSX 10.12.3, Chrome 57.0.2987.110 stable What steps will reproduce the problem? (1)Install any classic printer to OSX, create google cloud printer. (2)On any device, even the same as cloud printer host, open any google doc and in File->Page Setup chhose 'Landscape' orientation. (3)Print the document to cloud printer. What is the expected result? Landscape output What happens instead? Portrait output Video: https://drive.google.com/file/d/0B9rIuKmfZuLZZUFGbzRfLVFWRWM/view Issue is not reproducible when printing from google docs directly to printer. issue is reproducible on any printer connected per scenario. Issue is not reporducible on windows 10 cloud printer host in browser (not service).
,
Mar 30 2017
,
Mar 30 2017
Lei can you take a look to make sure that the Chrome Connector for OSX is respecting the orientation setting?
,
Jun 19 2017
Hi, Are there any updates on this issue? Is there something else we can gather through the tech case? Thanks!
,
Jun 27 2017
Reproduced again in QD5 under newly released 59.0.3071.115
,
Jun 27 2017
Lei, can you please advise if we have some plans to fix/check that?
,
Jun 30 2017
,
Oct 19 2017
Hi Lei, cloud print team, can we check that please, (still have opened cases and customer inquiring).
,
Feb 22 2018
This landscape/page orientation issue still plagues Chrome OS devices and Google Cloud Print. This really makes the printing experience sub-par. Chrome OS: Version 63.0.3239.140 (Official Build) (64-bit) Printer: Brother HL-5250DN Cloud Print: via Mac OS X shared printer
,
Sep 10
We have a customer experiencing the same issue: Chrome Version: 69.0.3497.81 (Official Build) (64-bit) OS Version: Sierra 10.12.6 I was able to reproduce under the same environment with Sierra, and High Sierra. I have not yet been able to test with the standalone connector. Job IDs and printer IDs from test environment: Print Job ID f94af54d-6d0c-08cc-1ec1-3eea3b320269 Printer ID 05213e81-85a6-06ad-cd23-19225a92a253 Print Job ID 530e63c6-2499-0ecf-db8a-366e11640fa6 Printer ID 58660b5b-735b-9cc0-b1c0-eb9819a22065
,
Sep 10
Lei, can we get some eyes on this one?
,
Sep 10
Just tried with the cloud print standalone connector, same issue occurs. In fact this issue goes beyond docs, and applies to anything printed from Chrome in this setup.
,
Sep 12
Pong. Thanks for bringing this back on my radar. It's not obvious how much work it will take to fix this, so I'm going to put Chrome 72 as the target milestone. If/when I get a better estimate, I will update this bug.
,
Nov 2
I can reproduce the problem, but only on Mac. I'll take a look. Usually, we are recommending that customers switch to the Cloud Print Connector. [1] However, there is no release package for Mac, and asking customers to build from source seems unreasonable. [1] https://github.com/google/cloud-print-connector
,
Jan 11
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 Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Jan 17
(6 days ago)
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. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by marchuk@chromium.org
, Mar 29 2017