Sort out dialog titles on CUPS add printer flow |
|||||||||||
Issue descriptionThere are (rather, are planned) 3 distinct ways a user can go through the add-printer CUPS flow: 1) The user selects a discovered printer, and that printer is configured without further input from the user 2) The user selects a discovered printer, but the system has to prompt them for manufacturer/model or ppd information 3) The user enters the full printer information without using any information from discovery. #1 is called "Adding a nearby printer" #3 is called "Adding a printer manually" #2 is somewhere in between, and is currently also uses the 'manually' terminology at the point where we start asking for information from the user. It was brought up on https://codereview.chromium.org/2825153002/ that this may be imprecise and/or confusing. We need to decide what the right thing to call that discover-then-add-more-information flow is, and make the associated changes if any.
,
May 12 2017
,
May 16 2017
My thoughts on this - There are 2 flows "Adding a nearby printer" or "Adding a printer manually" which should only be toggled on the first screen. The second screen for specifying the manufacturer/model for PPD download can occur (or not occur) for either workflow is a separate step to setting up a printer. No button should appear on this screen per crbug.com/721815 .
,
May 16 2017
Re#3: this issue is about the dialog title for the three flows. Flow 1 is called "Adding a nearby printer" and flow 3 is called "Adding a printer manually", but flow 2 is a little confusing since it's in between.
,
May 24 2017
Per convo with xdai@ this week, there are 2 flows for setup which may or may not need the dialog for manually providing the additional printer manufacturer and model information (both flows should ideally be able to auto-detect this information). For the dialog title, let's call it "Select a printer manufacturer and model" +shibasheikh@ - FYI.
,
Jun 12 2017
,
Aug 7 2017
,
Sep 6 2017
,
Oct 16 2017
,
Dec 11 2017
,
Jan 18 2018
It was fixed long time ago in https://codereview.chromium.org/2939233002.
,
Jan 19 2018
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by x...@chromium.org
, May 12 2017