Issue metadata
Sign in to add a comment
|
Chrome://settings page does not auto-refresh, after switching to a different wireless network |
||||||||||||||||||||||
Issue descriptionChrome Version: <From about:version: Google Chrome 60.0.3101.0> Chrome OS Version: <From about:version: Platform 9557.0.0> Chrome OS Platform: <Samus> Network info: <WiFi> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Go to chrome://settings page. (2) Click on WiFi, select a different wireless network Expected Result: The selected network when connected successfully should reflect on the chrome://settings page. Actual Result: chrome://settings page does not refresh to show the current connected network How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Sometimes Please provide any additional information below. Attach a screen shot or log if possible. Attached. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
May 16 2017
I'm not sure how the console error got triggered, but it is probably why the settings page is not updated correctly. There is a call to getManagedProperties that is not handling errors properly, I will fix that.
,
May 18 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/03bdb1e2d10e25f51ef62653fc3bff4c3e27e08c commit 03bdb1e2d10e25f51ef62653fc3bff4c3e27e08c Author: Steven Bennetts <stevenjb@chromium.org> Date: Thu May 18 20:55:20 2017 Settings: Network: Handle getmanagerProperties error correctly BUG= 722977 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation R=tbarzic@chromium.org Review-Url: https://codereview.chromium.org/2889843002 . Cr-Commit-Position: refs/heads/master@{#472925} [modify] https://crrev.com/03bdb1e2d10e25f51ef62653fc3bff4c3e27e08c/chrome/browser/resources/settings/internet_page/internet_known_networks_page.js
,
May 18 2017
,
Jan 22 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by steve...@chromium.org
, May 16 2017