Non-Regression : Unnecessarily WiFi is getting enabled on clicking 'Back' button in EULA screen |
|||||||
Issue descriptionChrome Version: 58.0.2994.0/9236.0.0 dev-channel Falco,Paine and Kip OS: Chrome What steps will reproduce the problem? (1)Recover build -> Go to 'Connect to network' screen (OOBE screen)--> Insert Mobile Dongle and ensure it is connected (2)Now from Uber Tray disable WiFi -> Select Cellular connection so that navigation to EULA Screen is seen (3)Click on 'Back' button in EULA screen -> 'Connect to network' screen is seen -> After 5-10 sec observe WiFi is enabled automatically (Please refer Video) Expected: WiFi should be enabled only after enabling 'WiFi' connection from Uber Tray Actual: Instead WiFi is enabled automatically on clicking 'Back' button in EULA screen This is Non-Regression Issue seen from M-55 @alemate : Please confirm the issue
,
Apr 10 2017
Hmm. The cr-network-select and the elements it uses *shouldn't* be enabling WiFi. That said, I can investigate for M-60 but will probably not be able to get to it for a couple of weeks (this doesn't seem super urgent since it shouldn't actually prevent a user from connecting to the Cellular device or accepting the EULA?).
,
May 25 2017
,
May 25 2017
,
Jun 30 2017
,
Sep 19 2017
,
Sep 19 2017
This is being triggered intentionally in NetworkScreenHandler::Show(): https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/chromeos/login/network_screen_handler.cc?q=network_screen&sq=package:chromium&l=92
,
Nov 29 2017
It would be weird to go to the network select screen and NOT have wifi turn on. I don't think we want to change the current behavior. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by alemate@chromium.org
, Apr 8 2017Owner: steve...@chromium.org