Worker: Provide a way to access parent frame task runners from a worker thread

third_party/WebKit/Source/core/workers/WorkerReportingProxy.h

Index: third_party/WebKit/Source/core/workers/WorkerReportingProxy.h
diff --git a/third_party/WebKit/Source/core/workers/WorkerReportingProxy.h b/third_party/WebKit/Source/core/workers/WorkerReportingProxy.h
index 523dbac39d373cc96625a4178f92579711f106bf..42cd9876f68192f46f47cf3063ec7be7eb5a8744 100644
--- a/third_party/WebKit/Source/core/workers/WorkerReportingProxy.h
+++ b/third_party/WebKit/Source/core/workers/WorkerReportingProxy.h
@@ -40,6 +40,7 @@
 namespace blink {
 
 class ConsoleMessage;
+class ParentFrameTaskRunners;
 class SourceLocation;
 class WorkerOrWorkletGlobalScope;
 
@@ -57,6 +58,9 @@ class CORE_EXPORT WorkerReportingProxy {
                                     SourceLocation*) = 0;
   virtual void postMessageToPageInspector(const String&) = 0;
 
+  // Returns the parent frame's task runners.
+  virtual ParentFrameTaskRunners* getParentFrameTaskRunners() = 0;

[kinuko, 2016/11/28 04:24:09]

This method as is might feel slightly misplaced to me.  If it's to be used only
for some reporting (is it?) it'd be nice to comment like that, or we might
rather want to update the class-level comment (&| naming) of this interface if
it could be used other than for reporting?

[nhiroki, 2016/11/28 05:29:26]

Good point. Now this looks a bit strange to me, too...

This ParentFrameTaskRunners is used for reporting worker activities by
WorkerReportingProxy or sending control messages (e.g., termination request) by
WorkerThread. This virtual interface is for the latter use. Maybe we could
remove this interface and then WorkerThread has its own ParentFrameTaskRunners
for control messages.

I'll work on it.

+
   // Invoked when the new WorkerGlobalScope is created. This is called after
   // didLoadWorkerScript().
   virtual void didCreateWorkerGlobalScope(WorkerOrWorkletGlobalScope*) {}