Allow for previous printing workflow to persist for user in CUPS workflow |
||
Issue descriptionUse Case: Existing Chromebook user had previously downloaded an extension/driver for printing made by a print provider. (ex. HP Print for Chrome) Enabling CUPS should not impact the existing printing workflow. We should allow the user to choose to switch. Expected behavior: - User updates to CUPS-enable version (M59). - Out of the box if they decide to print a doc, there should be no change/setup to the workflow from the Print Dialog.
,
Mar 1 2017
,
Mar 1 2017
Moved workflow updates for updating printer configuration to new bug: crbug.com/697276.
,
Mar 1 2017
After some discussions with xdai and further examination, I believe that I was wrong, flipping the cups flag will *not* break currently installed extension-based workflows. It *will* inhibit the notifications that guide a user to set that mechanism up for the first time, and the notification that a printer is ready to use if that mechanism has previously been set up. It may also lead to confusion as the CUPS flow comes online if users end up with multiple printer entries to print to the same printer.
,
Nov 5
|
||
►
Sign in to add a comment |
||
Comment 1 by weifangsun@chromium.org
, Mar 1 2017