New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 614702 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

Allow Google Cloud Print to Consider Local Print Restrictions

Project Member Reported by villegasanaya@chromium.org, May 25 2016

Issue description

Description:
To make Google Cloud Print honor the local printer queue settings; including color and queue restrictions.

Use case:
Administrators would use Google Cloud Print in a more efficient way, allowing them to save resources if needed, without having to use a third party appliance or application to manage the print details.

Motivation:
Financial, this can save resources to organizations if they are explicitly restricting the print mode and quotas.

Existing workarounds:
Using system print dialog which is not ideal.

 
Summary: Allow Google Cloud Print to Consider Local Print Restrictions (was: Enterprise support feature request)
Components: -Enterprise Internals>Printing
Labels: -Hotlist Hotlist-Enterprise-Support
Components: Services>CloudPrint
Can you clarify the scenario here? For example, is there some way to restrict a local color printer to not print in color... on Windows? And GCP is not respecting this restriction? Or are you saying GCP should have similar restriction features, like some local printers do?
Cc: bblietz@chromium.org
Cc: falcantara@chromium.org
Labels: Needs-Feedback
Cc: blumberg@chromium.org
On  bug 691671 , the bug reporter said "Google Cloud Chrome settings do have the option, and works as intended, but only for users signed into their Google Domain profile in the browser to pull the settings. The majority of users do not sign in."

That makes it sound like part of the request here may have already been implemented?
Status: Archived (was: Untriaged)
Archiving since there hasn't been a response. Happy to reopen if this is still an issue.

Sign in to add a comment