Step two of optionally sending messages to/from message ports as base::Value.

content/browser/web_contents/web_contents_impl.cc

Index: content/browser/web_contents/web_contents_impl.cc
diff --git a/content/browser/web_contents/web_contents_impl.cc b/content/browser/web_contents/web_contents_impl.cc
index 49b5a5eae016d5194ce73c86860209b4d8ff0c21..ede16421d7a0cfc89d2278a569153d4a6639cb64 100644
--- a/content/browser/web_contents/web_contents_impl.cc
+++ b/content/browser/web_contents/web_contents_impl.cc
@@ -4020,7 +4020,7 @@ void WebContentsImpl::RouteMessageEvent(
   // In most cases, we receive this from a swapped out RenderViewHost.
   // It is possible to receive it from one that has just been swapped in,
   // in which case we might as well deliver the message anyway.
-  if (!params.message_port_ids.empty()) {
+  if (!params.message_ports.empty()) {
     // Updating the message port information has to be done in the IO thread;
     // MessagePortMessageFilter::RouteMessageEventWithMessagePorts will send
     // ViewMsg_PostMessageEvent after it's done. Note that a trivial solution