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

Issue 853683 link

Starred by 2 users
Status: Duplicate
Merged: issue 859041
Owner:
yamaguchi@chromium.org
Closed: Aug 7
Cc:
tetsui@chromium.org
█ yoshiki@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Ubertray is not getting close automatically when any overlay is opened from it

Project Member Reported by rkalavakuntla@chromium.org, Jun 18 2018 
Chrome Version:69.0.3463.0/10793.0.0 dev-channel Daisy,Candy,Reks
OS:Chrome OS

What steps will reproduce the problem?
(1)Sign into user >> go to ubertray >> network section
(2)Click on any WiFi name to open 'Join WiFi network' and observe ubertray stays up.


Expected: Ubertray should automatically close after any overlay is opened
Actual: Instead, ubertray doesn't get closed automatically when any overlay is opened from it 

This is a Regression issue as same is working fine in 69.0.3457.0/10784.0.0 dev

Note: 
1.Issue is seen for all sub-overlays such as join WiFi, Pair Bluetooth device overlay etc..that are opened from Ubertray
2.Issue is seen also in OOBE
3.Issue is not applicable to Linux and Windows

Attached the screenshots for reference..
Actual.mp4
4.8 MB View Download
Expected.mp4
3.9 MB View Download

Comment 1 by rkalavakuntla@chromium.org, Jul 20

Cc: tetsui@chromium.org

Comment 2 by tetsui@chromium.org, Jul 23

Cc: -ajha@chromium.org -tetsui@chromium.org -brajkumar@chromium.org -tbuckley@google.com yamaguchi@chromium.org yoshiki@chromium.org
Owner: tetsui@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by tetsui@chromium.org, Aug 7

Cc: -yamaguchi@chromium.org tetsui@chromium.org
Labels: -M-69 M-70
Owner: yamaguchi@chromium.org

Comment 4 by yamaguchi@chromium.org, Aug 7

Mergedinto: 859041
Status: Duplicate (was: Assigned)
I think this duplicate of 859041.
69.0.3463.0 is a version around mid June. The fix was done in July. So I think this should have already been fixed on the later versions.
It did not repro on 70.0.3508.3, nor 69.0.3497.29.
►

Sign in to add a comment