[NetInfo] Browser changes to support connection.downlinkMax

content/common/view_messages.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // IPC messages for page rendering.
 // Multiply-included message file, hence no include guard.
 
 #include "base/memory/shared_memory.h"
 #include "base/process/process.h"
 #include "base/strings/string16.h"
@@ skipping 827 matching lines @@
 // to load the script, when the renderer send ViewHostMsg_CreateWorker before
 // the shared worker is killed only ViewMsg_WorkerScriptLoadFailed is sent.
 IPC_MESSAGE_ROUTED0(ViewMsg_WorkerScriptLoadFailed)
 
 // Sent when the worker has connected.
 // This message is sent only if the worker successfully loaded the script.
 IPC_MESSAGE_ROUTED0(ViewMsg_WorkerConnected)
 
 // Tells the renderer that the network type has changed so that navigator.onLine
 // and navigator.connection can be updated.
-IPC_MESSAGE_CONTROL1(ViewMsg_NetworkTypeChanged,
-                     net::NetworkChangeNotifier::ConnectionType /* type */)
+IPC_MESSAGE_CONTROL2(ViewMsg_NetworkConnectionChanged,
+                     net::NetworkChangeNotifier::ConnectionType /* type */,
+                     double /* max bandwidth mbps */)
 
 #if defined(ENABLE_PLUGINS)
 // Reply to ViewHostMsg_OpenChannelToPpapiBroker
 // Tells the renderer that the channel to the broker has been created.
 IPC_MESSAGE_ROUTED2(ViewMsg_PpapiBrokerChannelCreated,
                     base::ProcessId /* broker_pid */,
                     IPC::ChannelHandle /* handle */)
 
 // Reply to ViewHostMsg_RequestPpapiBrokerPermission.
 // Tells the renderer whether permission to access to PPAPI broker was granted
@@ skipping 571 matching lines @@
 // Instructs the browser to start plugin IME.
 IPC_MESSAGE_ROUTED0(ViewHostMsg_StartPluginIme)
 
 // Receives content of a web page as plain text.
 IPC_MESSAGE_ROUTED1(ViewMsg_GetRenderedTextCompleted, std::string);
 #endif
 
 // Adding a new message? Stick to the sort order above: first platform
 // independent ViewMsg, then ifdefs for platform specific ViewMsg, then platform
 // independent ViewHostMsg, then ifdefs for platform specific ViewHostMsg.