New issue
Advanced search Search tips

Issue 752696 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Navigation to chrome://settings/cupsPrinterDetails, doesn't display the details of added printer.

Project Member Reported by mkarkada@chromium.org, Aug 5 2017

Issue description

Chrome OS Version: M62 (62.0.3176.0 dev build)
Chrome OS Platform: 9807.0.0 dev channel caroline device

Steps To Reproduce:
(1) Goto Settings>Printers> ADD PRINTER> Configure a printer by providing required details on 'Add a printer manually' page.
(2) Navigate to chrome://settings/cupsPrinters, I can view settings>Printers page along with the printer name, that was added in step (1).
(3) Now navigate to chrome://settings/cupsPrinterDetails, printer details of the added one are not shown.
(4) If you select the printer and click on 3-dot menu>Details menu, now the printer details are visible.
  
Expected Result:
On navigation to chrome://settings/cupsPrinterDetails, it should display the details of added printer.

Please refer the attachments.
 
 
Screenshot 2017-08-04 at 3.36.50 PM.png
140 KB View Download
Screenshot 2017-08-04 at 3.37.07 PM.png
129 KB View Download
Labels: Proj-MaterialDesign-WebUI
Owner: x...@chromium.org
Status: Assigned (was: Untriaged)

Comment 2 by x...@chromium.org, Aug 8 2017

Status: WontFix (was: Assigned)
The printer detail page has been removed in https://chromium-review.googlesource.com/c/582271. 
If the printer detail page has been removed, then I suppose even the blank printer detail page should not be displayed. A blank page display would confuse the user.

Comment 4 by x...@chromium.org, Aug 15 2017

It's impossible to display a bland printer detail page any more.
I can still see a blank printer detail page (similar to second pic in #1) when I navigate to chrome://settings/cupsPrinterDetails.

I observed this on Chrome OS 9841.0.0, 62.0.3176.0 dev build.

Comment 6 by x...@chromium.org, Aug 15 2017

The CL in comment#2 was landed in 62.0.3177.0. So please verify the issue after it.
Sure, thank you for the update.

Sign in to add a comment