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

Issue 780798 link

Starred by 3 users
Status: Fixed
Owner:
alemate@chromium.org
Closed: Mar 2018
Cc:
█ krajshree@chromium.org
ajha@chromium.org
█ brajkumar@chromium.org
steve...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : 'Proxy settings' text is seen enabled even no network is connected in OOBE screen

Project Member Reported by mmanchala@chromium.org, Nov 2 2017 
Chrome Version: 64.0.3255.0/10090.0.0 dev channel Daisy,Candy and Reks 
OS: Chrome

What steps will reproduce the problem?
1)Recover build -> In OOBE screen click on 'Let's go' which navigates to 'Connect to netwok' screen
2)Now connect to Wi-Fi Network -> scroll down and click on 'Proxy settings' option
3)Now 'Network settings' window is seen -> Click on 'DISCONNECT' and close that Window
4)Now observe at Uber Tray Network is seen disconnected but 'Proxy settings' option is still seen enabled and try to click on it (Please refer Video)

Expected: 'Proxy settings' text should be seen disabled if no network is  connected
Actual: Instead 'Proxy settings' text is seen enabled 

This is Regression Issue as same is working fine in 62.0.3202.82/9901.66.0 stable-channel Candy

Note: 
1.'Next' button is also seen enabled when no network is available
2.Issue is also seen on 63.0.3238/10028.0.0

@alemate : Please confirm the Issue
Actual_EnabledOtion.mp4
18.9 MB Download
Actual_EnabledOptions.jpg
228 KB View Download

Comment 1 by mmanchala@chromium.org, Nov 2 2017 

Attaching Expected video and screenshot for reference
Expecte_DisabledOptions.mp4
11.1 MB View Download
Expected_DisabledOptions.jpg
298 KB View Download

Comment 2 by kbleicher@google.com, Dec 4 2017 

Hi, this is tagged as a beta blocker for M64.  We're not that far out and this bug hasn't been updated in a while.  Ping?  Thanks...

Comment 3 by kbleicher@google.com, Dec 7 2017 

M64 beta is targeted for next Tuesday (12-Dec); anything we can do to close this out and/or retag as stable block is appreciated.   I'll ping the owner as well.  Thanks!

Comment 4 by kbleicher@chromium.org, Dec 11 2017 

Please re-evaluate today (Monday, 11-Dec) re: Beta Blocker Status.  We're targeting Beta for tomorrow, so please update if a) this isn't blocking, b) the impacted boards can be identified, c) this is resolved / not reproducible, d) a merge / fix can be submitted today.  Thanks!

Comment 5 by gkihumba@google.com, Dec 12 2017

Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
Marking this as RBS. Disconnecting from network works fine and should not gate beta.

Comment 6 by kbleicher@chromium.org, Jan 4 2018 

Ping as this hasn't been updated since reported.  Tagged as a RBS.  Thanks

Comment 7 by josa...@google.com, Jan 20 2018

Cc: steve...@chromium.org
+steven too

Comment 8 by steve...@chromium.org, Jan 22 2018 

FWIW, this is a minor UI quirk and doesn't seem like a RBS issue to me.

Comment 9 by josa...@chromium.org, Jan 24 2018

Labels: -ReleaseBlock-Stable -M-64 M-65
Moving RBS and punting to M65 as per c#8

Comment 10 by alemate@chromium.org, Mar 13 2018

Status: Fixed (was: Assigned)
Fixed in M67. Likely in M66 too.
►

Sign in to add a comment