Try a workaround for initMessageEvent bug.

webkit/plugins/ppapi/message_channel.cc

 // Copyright (c) 2011 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.
 
 #include "webkit/plugins/ppapi/message_channel.h"
 
 #include <cstdlib>
 #include <string>
 
 #include "base/bind.h"
@@ skipping 288 matching lines @@
 bool MessageChannel::EvaluateOnMessageInvoker() {
   // If we've already evaluated the function, just return.
   if (NPVARIANT_IS_OBJECT(onmessage_invoker_))
     return true;
 
   // This is the javascript code that we invoke to create and dispatch a
   // message event.
   const char invoke_onmessage_js[] =
       "(function(window, module_instance, message_data) {"
       "  if (module_instance) {"
-      "    var message_event = window.document.createEvent('MessageEvent');"
-      "    message_event.initMessageEvent('message',"  // type
-      "                                   false,"  // canBubble
-      "                                   false,"  // cancelable
-      "                                   message_data,"  // data
-      "                                   '',"  // origin [*]
-      "                                   '',"  // lastEventId
-      "                                   null,"  // source [*]
-      "                                   []);"  // ports
+      "    var message_event = new MessageEvent('message', "
+      "                                         { data: message_data });"
       "    module_instance.dispatchEvent(message_event);"
       "  }"
       "})";
-  // [*] Note that the |origin| is only specified for cross-document and server-
-  //     sent messages, while |source| is only specified for cross-document
-  //     messages:
-  //      http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html
-  //     This currently behaves like Web Workers. On Firefox, Chrome, and Safari
-  //     at least, postMessage on Workers does not provide the origin or source.
-  //     TODO(dmichael):  Add origin if we change to a more iframe-like origin
-  //                      policy (see crbug.com/81537)
+  // Note that we purposely omit |origin| and |source|. The |origin| is only
+  // specified for cross-document and server-sent messages, while |source| is
+  // only specified for cross-document messages:
+  //  http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html
+  // This currently behaves like Web Workers. On Firefox, Chrome, and Safari
+  // at least, postMessage on Workers does not provide the origin or source.
+  // TODO(dmichael):  Add origin if we change to a more iframe-like origin
+  //                  policy (see crbug.com/81537)
 
   NPString function_string = { invoke_onmessage_js,
                                sizeof(invoke_onmessage_js)-1 };
   // Get the current frame to pass to the evaluate function.
   WebKit::WebFrame* frame =
       instance_->container()->element().document().frame();
   // Evaluate the function and obtain an NPVariant pointing to it.
   if (!WebBindings::evaluate(NULL, frame->windowObject(), &function_string,
                              &onmessage_invoker_)) {
     // If it fails, do nothing.
@@ skipping 85 matching lines @@
   //   SetPassthroughObject(passthrough_object());
   if (passthrough_object_)
     WebBindings::releaseObject(passthrough_object_);
 
   passthrough_object_ = passthrough;
 }
 
 }  // namespace ppapi
 }  // namespace webkit