summaryrefslogtreecommitdiffstats
path: root/net/base
diff options
context:
space:
mode:
authoroshima@chromium.org <oshima@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-22 20:08:05 +0000
committeroshima@chromium.org <oshima@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-11-22 20:08:05 +0000
commit354b8491e74c82b2c19c0e7f10ea9be2a71c6799 (patch)
treeb880d9df79017a2baaac287b0d064e70cb06dc64 /net/base
parentdafb7a0a867fbe26a4cff631d0b64bf5af43671e (diff)
downloadchromium_src-354b8491e74c82b2c19c0e7f10ea9be2a71c6799.zip
chromium_src-354b8491e74c82b2c19c0e7f10ea9be2a71c6799.tar.gz
chromium_src-354b8491e74c82b2c19c0e7f10ea9be2a71c6799.tar.bz2
Add delay when resuming load when network connection is restured.
Without delay, chrome silently fails to load the page. This is a wordaround and should be remoevd once the root cause is fixed. * Different delays for secure and non secure connection as secure connection needs longer delay. * I simply shortened proxy resolution as this may hit the same issue, and short enough that the page load happens after proxy resolution. BUG=chromium-os:8285 TEST=see the bug description for repro steps. Review URL: http://codereview.chromium.org/5156007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66990 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/base')
-rw-r--r--net/base/network_change_notifier_linux.cc10
1 files changed, 5 insertions, 5 deletions
diff --git a/net/base/network_change_notifier_linux.cc b/net/base/network_change_notifier_linux.cc
index 95f230d..1db4bd1 100644
--- a/net/base/network_change_notifier_linux.cc
+++ b/net/base/network_change_notifier_linux.cc
@@ -102,11 +102,11 @@ void NetworkChangeNotifierLinux::Thread::ListenForNotifications() {
if (HandleNetlinkMessage(buf, rv)) {
VLOG(1) << "Detected IP address changes.";
#if defined(OS_CHROMEOS)
- // TODO(zelidrag): chromium-os:3996 - introduced artificial delay to
- // work around the issue of proxy initialization before name resolving
- // is functional in ChromeOS. This should be removed once this bug
- // is properly fixed.
- const int kObserverNotificationDelayMS = 500;
+ // TODO(oshima): chromium-os:8285 - introduced artificial delay to
+ // work around the issue of network load issue after connection
+ // restored. See the bug for more details.
+ // This should be removed once this bug is properly fixed.
+ const int kObserverNotificationDelayMS = 200;
message_loop()->PostDelayedTask(
FROM_HERE,
method_factory_.NewRunnableMethod(