New issue
Advanced search Search tips

Issue 896222 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
ajha@chromium.org
benchan@chromium.org
dsunk...@chromium.org
steve...@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression : Dongle details page is still seen after removing Dongle

Project Member Reported by mmanchala@chromium.org, Oct 17 
Chrome Version: 70.0.3538.69/11021.51.0  0 dev-channel Kip,Daisy and Reks
OS: Chrome

What steps will reproduce the problem?
(1)Sign into User -> Insert Mobile Dongle and ensure it is connected
(2)Now at Uber Tray -> go to connected Dongle screen -> now click on 'Network settings' option -> chrome://settings window is seen
(3)Now click on Connected Dongle option -> Navigates to Dongle details page -> Now remove dongle and observe still Dongle details page is seen instead of navigating to chrome://settings page
(Please refer Video)

Expected: chrome://settings page should be seen after removing Dongle
Actual: Instead still Dongle details page is seen 

This is Regression Issue as same is working fine on M-69
Actual_Screen.mp4
17.7 MB Download

Comment 1 by mmanchala@chromium.org, Oct 17 

Attaching Expected video for reference
Expected_Navigation.mp4
15.2 MB Download

Comment 2 by harpreet@chromium.org, Oct 17

Cc: dsunk...@chromium.org benchan@chromium.org
Dinesh, can you please give this a try as well?

Comment 3 by dsunk...@chromium.org, Oct 29

Labels: M-70
I am struck with this bug which is blocking me for testing this scenario. 
https://bugs.chromium.org/p/chromium/issues/detail?id=899912

Hi Steven,
Can you please take a look at this issue?

Attaching the right label M-70 (as this issue is reported on M-70)

Comment 4 by steve...@chromium.org, Oct 29

Labels: -Pri-1 Pri-3
Why is this blocking issue 899912?

This doesn't seem like a high priority bug. We don't generally automatically navigate within UI. The "Out of Range" message is WAI.

Comment 5 by dsunk...@chromium.org, Oct 29 

issue 899912 is blocking because, that dongle is not getting detected on kernel versions 3.14

I can replicate this scenario using a coral device with kernel version 4.4. 

I guess based on UI changes, Steven confirms its WAI.

Comment 6 by steve...@chromium.org, Oct 29 

Yes, this is WAI. We could improve the UI, but it's a minor thing.

You can test issue 899912 by observing the system menu, or the main Settings page, both of which should update when the dongle is removed.
►

Sign in to add a comment