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

Issue 741514 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
pucchakayala@chromium.org
█ brajkumar@chromium.org
tbuck...@chromium.org
varkha@chromium.org
steve...@chromium.org
songsuk@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Bluetooth always seen enabled in Uber Tray even on disabling it.

Project Member Reported by jbanavatu@chromium.org, Jul 12 2017 
Chrome Version: 61.0.3154.0/9736.0.0 dev channel Paine
OS: Chrome OS

What steps will reproduce the problem?
(1)Sign in to chrome >> Open Uber Tray >> Go to Bluetooth 
(2)Now try disabling bluetooth by turning off the toggle button and Observe.

Expected: On turning off bluetooth toggle button, Blue tooth should get disabled.
Actual: Instead, it is still seen enabled.

This is regression issue as bluetooth gets disabled immediately after turning off bluetooth toggle button in 60.0.3112.50/9592.37.0 beta channel Paine.

Attaching screen cast for reference.

Note: Issue is not applicable to Linux, Windows & Mac OS
Actual.webm
3.9 MB View Download
Expected.webm
1.2 MB View Download

Comment 1 by tbuck...@chromium.org, Jul 27 2017

Cc: steve...@chromium.org tbuck...@chromium.org
Owner: varkha@chromium.org
+varkha, stevenjb

Is it possible it's just taking a really long time to disable bluetooth?

Comment 2 by varkha@chromium.org, Jul 27 2017

Cc: varkha@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
Tried it on dev channel samus (61.0.3159.8) and could not repro this. Also not sure I am the right owner for it at the moment, especially if it is an issue outside of UI or is device-specific.

Comment 3 by tbuck...@chromium.org, Jul 27 2017

Status: WontFix (was: Untriaged)
I also can't repro on 62.0.3166.0 canary Kevin, closing this as WontFix. Please re-open if it can be repro'd on a more recent build. If so, it might be hardware-specific.
►

Sign in to add a comment