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

Source/core/dom/MessagePort.cpp

Index: Source/core/dom/MessagePort.cpp
diff --git a/Source/core/dom/MessagePort.cpp b/Source/core/dom/MessagePort.cpp
index d9da4a2e26a76e97ed76ca6076dc57a389cf9513..4138eefee0ca69bdf033897ed8e87e7c582cf264 100644
--- a/Source/core/dom/MessagePort.cpp
+++ b/Source/core/dom/MessagePort.cpp
@@ -266,4 +266,16 @@ void MessagePort::trace(Visitor* visitor)
     EventTargetWithInlineData::trace(visitor);
 }
 
+v8::Isolate* MessagePort::scriptIsolate()
+{
+    ASSERT(executionContext());
+    return toIsolate(executionContext());
+}
+
+v8::Handle<v8::Context> MessagePort::scriptContext()
+{
+    ASSERT(executionContext());
+    return toV8Context(executionContext(), DOMWrapperWorld::mainWorld());

[jochen (gone - plz use gerrit), 2015/02/23 12:15:18]

what if the message port was created in an isolated world?

[Marijn Kruisselbrink, 2015/02/23 19:20:18]

That's a good question, and unfortunately not something I have an answer for. As
far as I know there is currently no way to actually figure out what world a
MessagePort was created in, and the best I'd be able to do would be some ugly
hack to take the world from some arbitrary message event, if there even is such
an event. But maybe I'm missing something obvious in the v8/blink integration?

+}
+
 } // namespace blink