Expose v8 context a MessagePort lives in to give content side code a valid context to (de)serialize…

Source/core/dom/MessagePort.h

Index: Source/core/dom/MessagePort.h
diff --git a/Source/core/dom/MessagePort.h b/Source/core/dom/MessagePort.h
index 69e6565ad5ef94f62d2a6550878394d00f6816fd..9e1601ef9ca115ac20c3cde60b89a839a0074f7f 100644
--- a/Source/core/dom/MessagePort.h
+++ b/Source/core/dom/MessagePort.h
@@ -112,6 +112,8 @@ private:
 
     // WebMessagePortChannelClient implementation.
     virtual void messageAvailable() override;
+    virtual v8::Isolate* scriptIsolate() override;
+    virtual v8::Handle<v8::Context> scriptContext() override;

[adamk, 2015/02/18 02:01:21]

Exposing a Context like this through the API worries me a little bit, as it's
easy to mishandle Contexts (memory leaks and security issues).

I looked at your Chromium change, but I'm not very familiar with
V8ValueConverter or base::Value; perhaps you can outline the high-level need you
have here?

     void dispatchMessages();
 
     OwnPtr<WebMessagePortChannel> m_entangledChannel;