Non-Regression : 'Network not available' screen is seen even after Wi-Fi is connected |
|||
Issue descriptionChrome Version: 65.0.3325.103/10323.45.0 beta-channel Daisy,Reks and Kip OS: Chrome What steps will reproduce the problem? (1)Recover build -> In OOBE screen click on 'Let's go' which navigates to 'Connect to network' screen -> Connect to Wi-Fi Network (2)Now at Uber Tray select 'Network' option ->Click on 'Network settings' -> Disconnect Network and Disable 'Configure IP address automatically' (3)Now at Uber Tray -> select 'Network' option and click on disconnected Wi-Fi network -> Wi-Fi gets connected -> Now click on 'Next' (4)In EULA screen click on 'Accept and continue' button -> 'Checking for updates' screen is seen for some time and now observe 'Network not available' is seen even Wi-Fi is connected (Please refer Video and Screenshot) Expected: Sign-in Screen should be seen after 'Checking for updates' screen Actual: Instead 'Network not available' is seen This is Non-Regression Issue seen from M-62 @stevenjb: Please confirm the Issue Note: 1)Issue is also seen in another scenario: a)Sign into User -> Go to chrome://settings page ->At 'Network' section click on Wi-Fi -> select Connected Wi-Fi network click on 'DISCONNECT' -> Disable 'Configure IP address automatically' -> click on 'Sign out' at Uber Tray -> Now in Sign out screen click on 'Add person' -> Observe 'Network not available' screen is seen (Please refer 'Actual_InSignOutScreen' Video) 2)Issue is also seen on M-63,M-64 and on Latest M-66 also
,
Feb 28 2018
Able to reproduce the Issue on 65.0.3325.107/10323.46.0 beta-channel Daisy,Candy and Reks
,
Feb 28 2018
This is a login / OOBE specific issue and may be a duplicate of a known issue. I believe the situation is not as straightforward as it seems. The network could be behind a cpative portal (or could have seemed like it was behind a captive portal when first connected) so we want to give the user the option to select a different network. In the new OOBE screen we should try to improve this experience, especially WRT captive portal detection. -> alemate@ to further triage.
,
Nov 8
Still present in 72.0.3593 |
|||
►
Sign in to add a comment |
|||
Comment 1 by mmanchala@chromium.org
, Feb 28 201817.1 MB
17.1 MB Download