Issue metadata
Sign in to add a comment
|
Enable toggle for WiFi and Cellular does not always accurately reflect the state |
||||||||||||||||||||
Issue descriptionChrome Version:61.0.3130.0/9655.0.0 dev channel Parrot OS:chrome What steps will reproduce the problem? (1)Sign in to user ->Launch chrome and Open chrome://md-settings (2)Near Wi-Fi section enable toggle button and Observe the movement (kindly refer video) Actual:Toggle enabling movement is not seen smooth Expected:Toggle enabling movement should be smooth This is a Regression as same is working fine in M-56 beta channel Parrot Note: 1.Issue is not applicable to Linux,Windows OS and also not seen in other chrome devices 2. Able to reproduce issue in M-58 @Stevenjb: Please confirm the issue.
,
Jul 24 2017
,
Aug 29 2017
,
Oct 2 2017
,
Oct 2 2017
,
Oct 3 2017
,
Oct 26 2017
,
Feb 14 2018
This is an even bigger issue with Cellular where requesting a disable is not always robust, depending on the timing. We need to introduce some extra logic to track what the UI has requested and attempt to reflect that in the model. We probably need an extra "enabling / dsiabling" state to properly reflect this.
,
Jan 12
Issue 833824 has been merged into this issue.
,
Jan 12
Per Tony's suggestion on duplicate issue 833824 , I believe the path forward should be as follows: "I propose we show a "Disconnecting..." subtitle and keep the toggle enabled after the user tries to disable the mobile data connection. Once we get notified by shill that the network is disabled we remove the subtitle and disable the toggle." Steven, are you still the appropriate owner for this issue?
,
Jan 14
Comment #10 generally sounds reasonable, especially for Cellular. I am not going to get to this anytime soon, so if it needs to be prioritized, please feel free to take this on. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by steve...@chromium.org
, Jun 20 2017