New issue
Advanced search Search tips

Issue 654649 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature

Blocking:
issue 604105



Sign in to add a comment

bluetooth: Grey out and disable chooser rows when devices are removed.

Project Member Reported by ortuno@chromium.org, Oct 11 2016

Issue description

On Android we can disable rows when the device is removed. We should add the same capability to the Desktop choosers.

 

Comment 1 by juncai@chromium.org, Oct 11 2016

So what is the purpose of grey out the removed device in the chooser? I thought just removing the removed device from the chooser is more straightforward for users?
Imagine that you're about to click on a device, and then we remove it. What do you wind up clicking on instead? Do you notice what you actually clicked on before clicking 'Pair'?

Comment 3 by juncai@chromium.org, Oct 11 2016

hmm... If a device is removed, then the entries of the chooser will change, and the user will probably notice, but also may not notice and then choose a wrong device.

So if a device is grey out, it will be in the chooser as long as the chooser is open?
Right.
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 12 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by scheib@chromium.org, Oct 19 2017

Labels: Hotlist-GoodFirstBug
Status: Available (was: Untriaged)
I would like to work on this. But could anyone please let me know how I can reproduce/verify this.
Project Member

Comment 8 by sheriffbot@chromium.org, Nov 21

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment